You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently require users to install it. But, unexpected behaviors may occur due to differences in mockgen behavior depending on which mockgen the user has installed.
Ideally, we should generate mocks without using user-installed mockgen and we can achieve that if we can import mockgen.
But currently, almost all logic of mockgen cannot be imported, because it is placed in main package.
So, I propose to fork golang/mock, add changes to make it importable, and use the fork to import mockgen.
We don't need to increment the major version for this change.
The mode of using user's mockgen is necessary (because some users may want to use a specific version of mockgen.) and will not be removed, so it is backward compatible.
Let's eliminate the need to install mockgen.
We currently require users to install it. But, unexpected behaviors may occur due to differences in mockgen behavior depending on which mockgen the user has installed.
Ideally, we should generate mocks without using user-installed mockgen and we can achieve that if we can import mockgen.
But currently, almost all logic of mockgen cannot be imported, because it is placed in
main
package.So, I propose to fork golang/mock, add changes to make it importable, and use the fork to import mockgen.
And, I raised the issue for golang/mock.
golang/mock#609
The text was updated successfully, but these errors were encountered: