Fixing mockery infinitely generating its own interfaces #640
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.
Description
Mockery currently will generate mocks for the interfaces it creates in its own auto-generated files. This is fixed by making the interface in-line in the function signature, which causes mockery to not attempt generating a mock for it.
TODO
Create integration test that asserts the number of files in the project over multiple mockery runs does not change.
Type of change
Version of Golang used when building/testing:
How Has This Been Tested?
Added a new fixture and config in mockery to test the "in-package recursive" behavior. It was confirmed manually that mockery no longer generates mocks for its own interfaces.
Checklist