[Yaml] Remove legacy parsing rule #46768
Merged
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
stof
approved these changes
Jun 24, 2022
fabpot
approved these changes
Jun 25, 2022
Member
|
Thank you @nicolas-grekas. |
nicolas-grekas
added a commit
that referenced
this pull request
Nov 14, 2022
…romNaN) This PR was merged into the 6.2 branch. Discussion ---------- [Yaml] Restore deprecated php/const: syntax in YAML key | Q | A | ------------- | --- | Branch? | 6.2 | Bug fix? | yes | New feature? | no | Deprecations? | yes | Tickets | Fix #48135 | License | MIT | Doc PR | - According to our BC policy, the change introduced in #46768 cannot be done without a deprecation notice. Unfortunately, the deprecation message is not displayed when reading the config. Commits ------- bcc2388 [Yaml] Restore deprecated php/const: syntax in YAML key
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
As far as I understood correctly, this part of the regexp has been introduced in #22878 to support a syntax that has been deprecated in #22913 and removed in 4.0.