Landon Clipp

Can you pinpoint this to a specific version of mockery where this bug was introduced?

Hi there. I think from a technical standpoint this is pretty easy to implement and sounds like a cool idea. The motivation for it however might be an anti pattern....

Definitely need to fix, this is a horrible behavior.

This seems like an unintended effect. Viper seems to be automatically mapping that env variable to the `Version` config. Can you just rename it to something else? Using `ARG` like...

Thanks for the report, this is indeed a bug. PRs would be very much appreciated! The correct way to handle something like this is probably to just add a number...

Hey there. The solution I recommend you use is use the .mockery.yaml file. This way the behavior will be cemented in your git repo (and version controlled). https://github.com/vektra/mockery#configuration

There is not a way to specify it but I know that cobra/viper provides facilities for defining variables from the environment. It would just need to be added to the...

Upon further thought, I realized that mockery probably needs to be modified so that it will search for `.mockery.yaml` on every path up to root of the CWD. go generate's...

So there have been requests in the past to add a `--packagesuffix` option which I previously put on hold because I wasn't sure how popular such a feature would be,...

It's possible it's not working correctly, if you can find where in the code it's causing this behavior, we can discuss in more specific detail. PRs are always welcome!