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
Certain commands have a set of flags (sometimes arguments associated to those flags).
How should this be handled?
The options available to "git remote" are pretty large, currently implemented is "git remote -v" and the code associated is passing along a "verbose" flag to the Remote class.
This imposes limitations into the Remote class (as it currently stands it expects the verbose argument). Would it be harmful to utilize kwargs inside of the class init methods?
Thoughts?
The text was updated successfully, but these errors were encountered:
I'd like to require all arguments at all times on Command classes, to be as explicit as humanly possible. Basically a command class should capture a given operation. The parser should be as intelligent as possible WRT to handling all their optional args/kwargs.
Certain commands have a set of flags (sometimes arguments associated to those flags).
How should this be handled?
The options available to "git remote" are pretty large, currently implemented is "git remote -v" and the code associated is passing along a "verbose" flag to the Remote class.
This imposes limitations into the Remote class (as it currently stands it expects the verbose argument). Would it be harmful to utilize kwargs inside of the class init methods?
Thoughts?
The text was updated successfully, but these errors were encountered: