Skip to content
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

Improve overriding of options #6

Open
YPares opened this issue Oct 26, 2018 · 0 comments
Open

Improve overriding of options #6

YPares opened this issue Oct 26, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@YPares
Copy link
Owner

YPares commented Oct 26, 2018

For now, the overriding of options goes like this:

Yaml file data section << Command line params << Physical files (both declared in locations and added with --loc)

This might not be intuitive. Let's say we have a record with a field called "fieldA", and located under "/Settings" in the resource tree. If a settings.json file is mapped to /Settings, and the user sets --fieldA stuff on the CLI, then this value (which would look like the definitive value) will be overriden by the value read in settings.json, even if intuitively the CLI options should override everything else.

Also if I say --loc /Settings+=settings.json on the command line, then I want whatever option read from settings.json to override all the rest, even if the final option is obtained from a file (and not directly from the CLI).

This means the exact source of each field should be tracked, and that the merge of the docrecords of options should be more intelligent.

@YPares YPares added the enhancement New feature or request label Oct 27, 2018
@YPares YPares changed the title Fix options overriding Improve overriding of options Oct 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant