[Yaml] Fix parsing inline anchored values#64388
Merged
nicolas-grekas merged 1 commit intoMay 28, 2026
symfony:6.4symfony/symfony:6.4from
nicolas-grekas:yaml-anchor-inline-fix-6.4nicolas-grekas/symfony:yaml-anchor-inline-fix-6.4Copy head branch name to clipboard
Merged
[Yaml] Fix parsing inline anchored values#64388nicolas-grekas merged 1 commit intosymfony:6.4symfony/symfony:6.4from nicolas-grekas:yaml-anchor-inline-fix-6.4nicolas-grekas/symfony:yaml-anchor-inline-fix-6.4Copy head branch name to clipboard
nicolas-grekas merged 1 commit into
symfony:6.4symfony/symfony:6.4from
nicolas-grekas:yaml-anchor-inline-fix-6.4nicolas-grekas/symfony:yaml-anchor-inline-fix-6.4Copy head branch name to clipboard
Conversation
Properly parse the value following an anchor in inline mappings and sequences instead of consuming it as part of a plain scalar. The lexer now tokenizes anchors and aliases as their own units, and the inline parser dispatches to the matching value parser after extracting the anchor name.
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.
Parsing inline YAML like
{ foo: &1 "FOO", bar: *1 }returned the value with surrounding quotes ('"FOO"') instead of unescaping the quoted scalar, and{ foo: &1 "${FOO}", bar: *1 }failed withMalformed inline YAML stringbecause the{inside the quoted value broke the lexer.Two issues combined:
lexUnquotedStringdid not recognize&and*as anchor/alias indicators, so it greedily consumed&NAME "valueand broke at the{of\${FOO}.&NAME "value"as a single plain scalar;REFERENCE_PATTERNjust captured the literal substring after the anchor name, so quotes and other value types were never parsed.This adds a dedicated
&/*token inlexInlineStructure, and aparseAnchorhelper inInlinethat extracts the anchor name before dispatching to the matching value parser (sequence/mapping/scalar). The fix also covers anchored sequences, mappings, and merge keys.