-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI Refactor #6571
Comments
9 tasks
Since this is a quite a big change. Could we add creating a doc to the to do list for this. Maybe as an upgrade doc or explaining the scope of the changes for projects dependent upon this area of code. |
@colin-axner sure, but the only major differences from a UX POV are:
We'll have an upgrading doc that will cover all of this stuff. |
This was referenced Jul 3, 2020
Merged
9 tasks
20 tasks
This was referenced Jul 20, 2020
Great job bez! Looking forward to the new cli |
9 tasks
alessio
pushed a commit
that referenced
this issue
Aug 17, 2020
Closes: #7007 Ref: #6571 Co-authored-by: Aaron Craelius <[email protected]> Co-authored-by: Alessio Treglia <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The current state of the CLI in the SDK is a bit of a mess, with the use of Viper global/singleton, ad-hoc flag instantiation and binding, and magically instantiation of
client.Context
. It makes testing difficult and runtime errors hard to debug.Proposal
Once #6423 is finalized and merged, we'll have the ability to remove a lot of the existing cruft from the CLI framework. Namely, we should:
client.Context
Init*
andNew*
functions - Context: Remove Init/New #6797Stretch Goal:
--config
flag where if provided, any field found will set/override any flag/arg./cc @aaronc @anilcse @sahith-narahari @alessio
For Admin Use
The text was updated successfully, but these errors were encountered: