-
Notifications
You must be signed in to change notification settings - Fork 4
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
Expose all or most config options to the CLI #50
Comments
It should be noted that some CLI options are not config options. This excersize should be adding each config option as CLI arguments. There would need to be a decision about which one wins when both are provided: my initial reaction is that CLI arguments should override options specified in |
#62 exposes 4 more options as CLI arguments, but I'm considering support for These particular args could potentially be exposed as a single glob pattern (therefore a single string value, much like the example I'd be open to some explicit new options that are glob patterns and override the aforementioned config behaviour - obviously, this is a bit more involved. |
See follow up issue: #63 |
This is achievable with
fta.json
configuration.. it'd be nice to have the same flags in the CLIThe text was updated successfully, but these errors were encountered: