Fix YAMLDecoder to support merging anchors#238
Merged
Conversation
Collaborator
Author
|
I should have opened an issue first. This might not actually fix the issue. Regardless I should probably add tests, changelog, etc. |
Owner
|
Thanks for the change! It looks right to me, but I'd like to see the tests and changelog entry as you mentioned. No need to file a separate ticket for the issue you're trying to resolve. |
Currently `YAMLDecoder` uses `Resolver.basic` instead of `Resolver.default`, since it doesn't need to resolve types. This has the side effect of not including `.merge` as an option, making `decode` fail to see anchored properties.
Collaborator
Author
|
@jpsim I fixed the fix, added some tests, and updated the changelog. |
Owner
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently
YAMLDecoderusesResolver.basicinstead ofResolver.default, since it doesn't need to resolve types. This has the side effect of not including.mergeas an option, makingdecodefail to see anchored properties.