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
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’s 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
The text was updated successfully, but these errors were encountered:
@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?
🚀 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
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
The text was updated successfully, but these errors were encountered: