-
Notifications
You must be signed in to change notification settings - Fork 412
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
Makefile fix, and tests refactoring #399
Conversation
There's no reason not to keep them, it's just auto-generated stuff. Running mockery on the repo again would re-create them. If you re-submit with the mocks added back I can approve. |
1f7a28c
to
577b7a5
Compare
@LandonTClipp thanks for your time! The thing with "running mockery again" is that it was run incorrectly before. You had to do it manually somehow (not versioned in Makefile) and it didn't work out of the box. When I run the
If you still think I should add them back, then no problem, I'll modify the Makefile to include them, but I think it's just dead code and in the past it was included by an accident (by running |
577b7a5
to
45dc76a
Compare
Looks good to me, thanks for the cleanup! |
Happy to help :-) |
I'm not sure if mocks like
mocks/cmd/stackTracer.go
were being generated for a reason, if so then I can add them back. However, they were not used anywhere so I went ahead and deleted them.