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
In OmegaConf 2.0, it is possible to have empty elements in a list of resolver arguments, for instance:
${foo:a,}
foo("a", "")
${foo:a,,b}
foo("a", "", "b")
${foo:,}
foo("", "")
This has been deprecated in OmegaConf 2.1. Users should instead use explicit empty strings, for instance:
${foo:a,""}
${foo:a, '', b}
${foo:"", ""}
The text was updated successfully, but these errors were encountered:
Add tests and news fragment
9ecac27
Fixes omry#572
5a7bccb
Successfully merging a pull request may close this issue.
In OmegaConf 2.0, it is possible to have empty elements in a list of resolver arguments, for instance:
${foo:a,}
callsfoo("a", "")
${foo:a,,b}
callsfoo("a", "", "b")
${foo:,}
callsfoo("", "")
This has been deprecated in OmegaConf 2.1. Users should instead use explicit empty strings, for instance:
${foo:a,""}
${foo:a, '', b}
${foo:"", ""}
The text was updated successfully, but these errors were encountered: