Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #966
This PR adds the capability to decode multiple merge nodes on a given document - eg, the document
will now decode to
where previously, it would have returned an error saying that the
merged
mapping had a duplicate key<<
.While this behaviour isn't in the YAML spec (the blessed way to do multiple merges is
<<: [*one, *two]
), it's also not disallowed by it, and many yaml libraries for other languages - notably Python's pyyaml and Ruby's psych, which is backed by libyaml - do support this behaviour.Multiple issues (#966, #918) on this have been raised on this repo before, which leads me to believe that using multiple merge keys is a relatively common expectation to have for a yaml library.