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
Is your feature request related to a problem? Please describe.
In out init, we sometime set some flag's default based on parsed flags. For example, when moving data between servers, we use the values of some flags for the first server as defaults for the other server(s). It is currently possible, except for required flags where the parse fails the validation.
In some cases where multiple command are for a type of environment, we have a base class shared by those commands. In that base init, it would also be nice to do a parse without validation failure for the flags in the derived classes.
Describe the solution you'd like
It would be nice to be able to parse without validation.
Describe alternatives you've considered
Our current workaround is to save the required values, reset the required values, parse and restore the required values.
Is your feature request related to a problem? Please describe.
In out
init
, we sometime set some flag's default based on parsed flags. For example, when moving data between servers, we use the values of some flags for the first server as defaults for the other server(s). It is currently possible, except forrequired
flags where theparse
fails the validation.In some cases where multiple command are for a type of environment, we have a base class shared by those commands. In that base
init
, it would also be nice to do aparse
without validation failure for the flags in the derived classes.Describe the solution you'd like
It would be nice to be able to
parse
without validation.Describe alternatives you've considered
Our current workaround is to save the
required
values, reset therequired
values,parse
and restore therequired
values.Additional context
Related to #854 and #829.
The text was updated successfully, but these errors were encountered: