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
OmegaConf.update() behavior when the input value was a list or a dictionary was to assign the value instead of to merge it:
cfg = OmegaConf.create({"a": {"b": 10}}) OmegaConf.update(cfg, "a", {"c": 20}}) # cfg is now {"a": {"c": 20}}
The intended behavior for update lines up better with a merge:
OmegaConf.update(cfg, "a", {"c": 20}}) # cfg is now {"a": {"b": 10, "c": 20}}
To support both use cases, a new merge flag is introduced to update:
merge
def update( cfg: Container, key: str, value: Any = None, merge: Optional[bool] = None ) -> None:
The default value for merge will become True in a future version. To avoid unexpected behavior changes, please call update with merge=[True|False].
merge=[True|False]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
OmegaConf.update() behavior when the input value was a list or a dictionary was to assign the value instead of to merge it:
The intended behavior for update lines up better with a merge:
To support both use cases, a new
merge
flag is introduced to update:The default value for merge will become True in a future version.
To avoid unexpected behavior changes, please call update with
merge=[True|False]
.The text was updated successfully, but these errors were encountered: