-
Notifications
You must be signed in to change notification settings - Fork 90
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
if my package imports another package of the same name, the fake imports both #8
Comments
👍 also stumbled over this. |
We also ran into this. Any ideas on how we might fix this? We could change the package or the imports, but we'd rather not do either, as the package we're counterfeiting is purposely named the same as the package it imports as we are shadowing. e.g.
|
Running into this issue as well. A simple solution would be to allow counterfeiter to generate a source file within the same package as the counterfeited interface. Is there any particular reason that the "${pkgname}/fakes" package was chosen? |
@devoid That said, I think that this should be fixed. Any takers? Would love to help anyone that wants to work on a PR for this. |
Is this still an issue in v6.0.0? |
with:
running:
counterfeiter . Source
results in:
it should probably not
The text was updated successfully, but these errors were encountered: