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

Generalize disambiguation of CLI arguments #63

Open
YPares opened this issue Oct 9, 2019 · 0 comments
Open

Generalize disambiguation of CLI arguments #63

YPares opened this issue Oct 9, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@YPares
Copy link
Owner

YPares commented Oct 9, 2019

( This might be unnecessary if #47 is tackled )

For now, the flag names for the CLI are generated by inspecting each DocRec independently of the others. That means that if two DocRec of options at two different points in the pipeline both expose a field with the same name, only the first one will be exposed via CLI (the second is still settable in the config file, though).

There is a disambiguation method, but currently it works only at the level of one DocRec (if two fields, named with their two "paths" p1 and p2, are so that last p1 == last p2). This feature is rarely used because few tasks make use of the hierarchical nature of DocRec names (most use only one-level namings). We should extend that disambiguation process to the whole pipeline.

@YPares YPares added the enhancement New feature or request label Oct 14, 2019
@YPares YPares changed the title Fix disambiguation of CLI arguments Generalize disambiguation of CLI arguments 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