Exempt custom_-prefixed YAML fields from strict validation - #9795
Open
avaitla wants to merge 2 commits into
Open
Exempt custom_-prefixed YAML fields from strict validation#9795avaitla wants to merge 2 commits into
custom_-prefixed YAML fields from strict validation#9795avaitla wants to merge 2 commits into
Conversation
Unknown fields prefixed with `custom_` are reserved for user-defined metadata and no longer fail strict YAML parsing, at any nesting depth. All other unknown fields still produce a parse error. Closes rilldata#9794
avaitla
marked this pull request as ready for review
August 7, 2026 01:35
Adds a note to the YAML Syntax overview (generated from the project schema) explaining that unknown fields prefixed with `custom_` are ignored by validation and can hold user-defined metadata.
nishantmonu51
added
Type:Feature
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.
Unknown fields prefixed with
custom_are reserved for user-defined metadata and no longer fail strict YAML parsing, at any nesting depth. All other unknown fields still produce a parse error.Closes #9794
What we've tried to do here is simply silence the errors (by filtering them out) and keeping the change as simple and surgical as possible.
Checklist: