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
I was updating monorepo with services from v0.75.0 and discovered that you have got rid of cli arguments in favour of config options. The only two that we were using were no-client/no-server and I believe we are not the only with this use case. Maybe you can consider returning these options? Or maybe introduce some config overriding mechanism through cli? I think smth like -override="generator.features.disable+'paths/client'" would work perfectly (maybe there are some opensource yaml cli overrides already)
We have 10+ specs and therefore the same amount of //go:generate go run ... lines and it is pretty annoying to write two configs to do smth like -config=./noclient.yaml instead of just using -no-client where it was appropriate
The text was updated successfully, but these errors were encountered:
Description
I was updating monorepo with services from v0.75.0 and discovered that you have got rid of cli arguments in favour of config options. The only two that we were using were no-client/no-server and I believe we are not the only with this use case. Maybe you can consider returning these options? Or maybe introduce some config overriding mechanism through cli? I think smth like
-override="generator.features.disable+'paths/client'"
would work perfectly (maybe there are some opensource yaml cli overrides already)We have 10+ specs and therefore the same amount of
//go:generate go run ...
lines and it is pretty annoying to write two configs to do smth like-config=./noclient.yaml
instead of just using-no-client
where it was appropriateThe text was updated successfully, but these errors were encountered: