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
The current kci command line tool is based on the same code as in the legacy tools kci_build, kci_test etc. As part of needing a redesign, it's worth considering alternative packages such as click and typer (which is based on click).
Investigating whether we can use them and comparing them can be done by implementing the basic support for loading settings values from TOML for the current command, looking up TOML settings groups based on a config name (e.g. to find an API token for a particular API instance config), implementing some dummy nested commands as well as a real whoami command as a proof-of-concept.
The current
kci
command line tool is based on the same code as in the legacy toolskci_build
,kci_test
etc. As part of needing a redesign, it's worth considering alternative packages such asclick
andtyper
(which is based onclick
).Investigating whether we can use them and comparing them can be done by implementing the basic support for loading settings values from TOML for the current command, looking up TOML settings groups based on a config name (e.g. to find an API token for a particular API instance config), implementing some dummy nested commands as well as a real
whoami
command as a proof-of-concept.click
[RFC] kci-click: add kci PoC using Click #2111typer
[RFC] kci-typer: add kci PoC using Typer #2112The text was updated successfully, but these errors were encountered: