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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve later when using parser_mode="omegaconf" #461

Open
roytseng-tw opened this issue Feb 29, 2024 · 1 comment
Open

Resolve later when using parser_mode="omegaconf" #461

roytseng-tw opened this issue Feb 29, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@roytseng-tw
Copy link

馃殌 Feature request

Provide an api like parser.resolve_omegaconf(...) to manually trigger the resolving on omegaconf node values.

Motivation

Current omegaconf mode has some limitations as described in the doc

The parser_mode='omegaconf' provides support for OmegaConf鈥檚 variable interpolation in a > single yaml file. It is not possible to do interpolation across multiple yaml files or in an isolated individual command line argument.

With the newly proposed api, after loading config from the file and command line, one can manually trigger value resolving across config file and command line arguments.

Pitch

Alternatives

@roytseng-tw roytseng-tw added the enhancement New feature or request label Feb 29, 2024
@mauvilsa
Copy link
Member

mauvilsa commented Mar 7, 2024

@roytseng-tw thank you for the proposal. The motivation isn't very clear. In the jsonargparse docs it does say that interpolation across config files is not supported, and a new feature could be to add support for it. However, why is it that you say "manually trigger" resolving? Why does this have to be manual? What are real use cases in which such a manual step is necessary?

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

2 participants