-
Notifications
You must be signed in to change notification settings - Fork 393
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
Logging warning when mock config is orphaned #764
Labels
approved feature
Feature request approved for development
Comments
This should be very easy to add. Initially, we should only add a warning log to retain backwards compatibility. I'm approving this feature request to add a log. I do not want mockery to mutate the config, or delete old mock files, however. Removal of user's mocks should be the user's responsibility, as there are too many edge cases for mockery to handle it properly. |
LandonTClipp
changed the title
Auto removing orphan mocks
Logging warning when mock config is orphaned
Mar 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mockery Version
v2.42.0
Golang Version
go1.22.0 amd64
Installation Method
Steps to Reproduce
Expected Behavior
Since interface doesn't exists anymore, I would have expected mockery command to error or something because there is a misleading/redundant reference in config.
Actual Behavior
Physical mock file is still in the codebase but unfortunately it is redundant because there is no interface for it anymore.
The text was updated successfully, but these errors were encountered: