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
I've found an issue using a YAML data source that contains anchors, aliases and merge keys. Specifically, it seems that merge keys may not be fully resolved / materialized to the anchor value once the YAML is loaded, which can cause problems working with other features.
For example, merge will not work with a mapping value which uses a merge key:
This turned out to be a bit more complicated than I expected, and I'm only just now getting back to it. This is an upstream bug in the YAML library I'm using: go-yaml/yaml#139 (comment)
Thankfully now I understand the problem and will be able to work around it 😉
Hi 👋 ,
I've found an issue using a YAML data source that contains anchors, aliases and merge keys. Specifically, it seems that merge keys may not be fully resolved / materialized to the anchor value once the YAML is loaded, which can cause problems working with other features.
For example,
merge
will not work with a mapping value which uses a merge key:alias.yaml
:I can coerce the alias to the anchor's value by round-tripping it to get the expected result:
The issue seems specific to using merge keys. We can use an alias without issue:
The text was updated successfully, but these errors were encountered: