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
And to add new mock on config, users have to execute cmd like this, and config for new mock will be added on gomockhandler.json. gomockhandler -config=/path/to/gomockhandler.json -source=foo.go -destination=./mock/ [other mockgen options]
But, PR reviewers cannot see what command will be registered, and it makes PR review a little hard.
So, I want to add new optional configuration file or add information on config file to resolve this.
The text was updated successfully, but these errors were encountered:
sanposhiho
changed the title
support more readable configuration file to generate mock
make mockgen command more readable on configuration
Sep 17, 2021
sanposhiho
changed the title
make mockgen command more readable on configuration
configuration file is not readable
Nov 12, 2021
I think we can resolve this by splitting gomockhandler.json into two file. The one is to manage mock information (= configuration file) and the other one is to manage the status of each mock.
With this, we can make configuration file(the first one) more readable. And we can allow user to edit configuration file directly (= user can edit configuration without CLI)
close this issue and open another enhancement issue.
Now, we support configuration
gomockhandler.json
.And to add new mock on config, users have to execute cmd like this, and config for new mock will be added on gomockhandler.json.
gomockhandler -config=/path/to/gomockhandler.json -source=foo.go -destination=./mock/ [other mockgen options]
But, PR reviewers cannot see what command will be registered, and it makes PR review a little hard.
So, I want to add new optional configuration file or add information on config file to resolve this.
The text was updated successfully, but these errors were encountered: