Omry Yadan
Omry Yadan
Probably too big of a change for 2.1 at this point.
DictConfig does not normally expose the internal representation during debugging because it's not as useful as seeing the user level content. Why are you asking?
I believe the debugger is using `_dir_` to list the object fields as well and not overriding dir would result in fields that are not meant to be user visible...
As you are pointing out, merge is NOT a write operation as it creates a new config. This is by design and makes perfect sense to me.
By the way, there is an undocumented cfg.merge_with() function that does perform an inline write. This should fail if the dest config is read only.
This is arguably an accidental feature. It enables the usage of the literal string `???`. What is the use case for a resolver to return a MISSING value?
The behavior you are describing sounds like a bug: merge is not supposed to resolve interpolations (except interpolation to container nodes, that has a special treatment).
Can you provide a minimal snippet of what you are doing with an explanation of the desired behavior?
This is a feature request, not a bug. Interpolation into a list using negative index never worked (and this is the first time someone asks for it). It only seems...
> > Using the supported syntax in 2.0 will look like this: > > FYI the `"${list.-1}"` syntax is not working for me. > I tried it on the 2.0...