mockery v3 is GA and includes Moq templates

[LandonTClipp]

I just released mockery v3! Users of moq should be able to migrate over to mockery and use the template: matryer config parameter.

@breml has already done this and has been a huge help in making this migration smoother for moq users. There likely still exist some caveats and corner cases I have not teased out, so please let me know if you find anything.

After a certain point, I would suggest putting https://github.com/matryer/moq into maintenance-only mode, or even archive it, once we've confirmed that all necessary features have been properly represented in mockery.

Feel free to also read my announcement on my personal blog site that explains more of the history and intentions of mockery.

CC @matryer @sudo-suhas.

[frozenbonito]

@LandonTClipp
I'm interested in migrating to mockery.
What do you think about adding new features to mockery's moq template that are not available in the original moq?
For example, I would be happy if a feature like #226 (implemented in #227) could be added to mockery.

[breml]

@frozenbonito I am not completely sure, but I think your feature would not even require any addition to mockery, since you can define the templates, that are used to generate the mocks, yourself. You can also provide "template data" in the mockery config file. So I guess, it would be possible to define a template, derived from the original moq template, that is extended in the way you require. The actual interfaces, that should be embedded can be provided in the config file.

I recommend, that you give it a try.

Links:

• template for matryer/moq
• Example for "template data"

[LandonTClipp]

@frozenbonito that's a really interesting idea. I of course would love to add more features, but I do have to weigh it against the maintenance burden I incur when new features are added. I would encourage you to submit an issue requesting something like this and we can see how much attention it gets. I get feature requests all the time and I can't possibly field all of them, so I have to pick the ones that are most broadly desirable 😄

@breml points to a solution that I think will work very well for your use case, although all this does is it shifts the maintenance burden to you instead of me! Pick your poison I guess.

[frozenbonito]

@LandonTClipp
Thank you for your reply.
I would like to create an issue for the feature request later.
If it seems acceptable, I can also create a Pull Request.