Open samherrmann opened 1 year ago
My current workaround is to use the -skip-ensure
flag. This workaround prevents me from having to manually modify the generated mock file, which is crucial because this allows go generate ./...
to be re-run on the project without overwriting manual changes.
This issue is to track the limitation that was mentioned in the description of #175.
Consider the following interface:
When generating a mock using moq v0.3.2, the following implementation check is created:
This code is not valid due to the following reason: