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
Ideally all of the configurable options from the JSON configuration can be passed in directly to the CLI. If all of the required options are passed in then the settings in the JSON file are not necessary. This means we:
can either "mix and match" where the CLI options can take priority over the same setting in the configuration (allowing both to be used together)
we can pass in a --no-config option and all required configurations would need to passed in via the command line, throwing relevant errors if invalid or missing configuration is found
Documentation should be added to the README about the usage (in the form of a --help page output) with example commands
The text was updated successfully, but these errors were encountered:
I can see this being a feature for the long term, where sane defaults can be enforced but I dont think its that important for us to try and get rid of the configuration file completely, but instead, passing in the configuration options via the command line should overwrite settings in the config file. I see this being a better short-term solution to bring some flexibility to keeli (especially in CI)
Ideally all of the configurable options from the JSON configuration can be passed in directly to the CLI. If all of the required options are passed in then the settings in the JSON file are not necessary. This means we:
--no-config
option and all required configurations would need to passed in via the command line, throwing relevant errors if invalid or missing configuration is foundThe text was updated successfully, but these errors were encountered: