-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to generate exported mock type for internal interfaces #191
Comments
I really like this idea. I'll tag this for consideration. |
This option would help me. I have a problem when the mocks on private interface are generated in a different folder than the origin package. It tries to import to origin interface but compilation of the generated mock fails as the interface is private and the import comes from another package. Edit: I just looked at #234 (I'll try it thanks. But it's a workaround in my opinion) |
@matcornic Adding this feature would be pretty trivial. The provided example in the OP with |
#Hi,
Great tool, I really like it! Is there a possibility to add a new option like
-exported=true
, which will make internal interfaces exported?Please consider an example:
It could generate a mock type in
automock
package with a nameFoo
, which is easy to use in test files.Alternative:
It could generate a constructor for this type, which can be used from outside of the
automock
package.The text was updated successfully, but these errors were encountered: