docs: clarify YAML type expressions vs signature short names#1084
Draft
benbellick wants to merge 9 commits into
Draft
docs: clarify YAML type expressions vs signature short names#1084benbellick wants to merge 9 commits into
benbellick wants to merge 9 commits into
Conversation
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
1 participant
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.
Extension YAML type fields use the type expression grammar, while function references use signature short names. The docs now call out that distinction directly and the schema description reinforces it for YAML type-valued fields. This also fixes the test README description of
vbinto refer to variable-lengthbinary.Note: This PR was developed with AI assistance. All changes have been reviewed, and I take full responsibility for this contribution.
This change is