Revert "Fixing #291 where a different import with the same name as the package would not get included in the mock" #303
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #297
This is causing an issue when generating mocks:
The fact that this passed CI means that we need to revisit it. I'm thinking that CI should, as part of perhaps a larger integration test, have mockery actually build the mocks and then run the test suite. This will catch errors like this. Although, I could have sworn that checks for validity were already done in the unit tests? I'm not sure.