Add decode option that allows specific field prefixes#795
Merged
goccy merged 1 commit intogoccy:masterfrom Oct 21, 2025
Merged
Conversation
This would be paired with DisallowUnknownField where you generally want to make sure the yaml does not have unknown fields, but allow for cases where the yaml has some extra stuff in it, e.g. for custom metadata or using fields as variables for anchors. In our specific case we allow `x-*` fields for these cases. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #795 +/- ##
==========================================
+ Coverage 77.97% 78.00% +0.02%
==========================================
Files 22 22
Lines 8108 8119 +11
==========================================
+ Hits 6322 6333 +11
Misses 1370 1370
Partials 416 416 🚀 New features to boost your workflow:
|
Contributor
Author
|
ping @goccy |
Owner
|
LGTM 👍 |
Madoxen
pushed a commit
to barney-ci/go-yaml
that referenced
this pull request
Jan 27, 2026
This would be paired with DisallowUnknownField where you generally want to make sure the yaml does not have unknown fields, but allow for cases where the yaml has some extra stuff in it, e.g. for custom metadata or using fields as variables for anchors. In our specific case we allow `x-*` fields for these cases. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
wrouesnel
pushed a commit
to wrouesnel/go-yaml
that referenced
this pull request
Feb 12, 2026
This would be paired with DisallowUnknownField where you generally want to make sure the yaml does not have unknown fields, but allow for cases where the yaml has some extra stuff in it, e.g. for custom metadata or using fields as variables for anchors. In our specific case we allow `x-*` fields for these cases. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
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
3 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.
This would be paired with DisallowUnknownField where you generally want to make sure the yaml does not have unknown fields, but allow for cases where the yaml has some extra stuff in it, e.g. for custom metadata or using fields as variables for anchors.
In our specific case we allow
x-*fields for these cases.Before submitting your PR, please confirm the following.