We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
a.b.c: 1
This is a clarification question as we use OmegaConf to support our configuration system.
Omegaconf support an API with . syntax, i.e. Omegaconf.select("a.b.c"). This implicitly assume that the internal dictionary is a nested dictionary.
.
Omegaconf.select("a.b.c")
For this example
conf = {"a.b.c": 1} omega_conf = Omegaconf.create(conf) omega_conf.select("a.b.c") # Return nothing omega_conf["a.b.c"] # Return 1
Is using nested . key discouraged with OmegaConf or is this a bug? I cannot find any example in the docs so I am raising this issue.
OmegaConf
In case flat key is a bad practice, would you be open to support OmegaConf.create converts flat key to nested dict automatically?
OmegaConf.create
The text was updated successfully, but these errors were encountered:
This isn't a bug. I'll follow-up in #1188 to avoid duplicated discussions.
Sorry, something went wrong.
No branches or pull requests
This is a clarification question as we use OmegaConf to support our configuration system.
Omegaconf support an API with
.
syntax, i.e.Omegaconf.select("a.b.c")
. This implicitly assume that the internal dictionary is a nested dictionary.For this example
Is using nested
.
key discouraged withOmegaConf
or is this a bug? I cannot find any example in the docs so I am raising this issue.In case flat key is a bad practice, would you be open to support
OmegaConf.create
converts flat key to nested dict automatically?The text was updated successfully, but these errors were encountered: