-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[YAML] Usage of PHP constant in YAML keys fails on 3.3 #22854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I don't think the parser is able to parse this tag as a key, that's why we should remove the |
I confirm it worked and it doesn't anymore |
Can you please try #22878? |
@xabbuh working on it |
@xabbuh I have an error:
on It may be related to the notice of @chalasr on your PR. I can't debug easily right now, let's wait tomorrow :) . |
This PR was merged into the 3.3 branch. Discussion ---------- [Yaml] parse PHP constants in mapping keys | Q | A | ------------- | --- | Branch? | 3.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #22854 | License | MIT | Doc PR | Commits ------- ae52fe6 [Yaml] parse PHP constants in mapping keys
Uh oh!
There was an error while loading. Please reload this page.
The following file was valid on 3.2 and its parsing fail on 3.3:
https://github.com/EnMarche/en-marche.fr/blob/fce5e06a50fa87b3416e6bb9dee13f1bafe000f4/app/config/services/workflows.yml#L14
https://circleci.com/gh/EnMarche/en-marche.fr/4428
It seems to be related to the usage of PHP constants as keys:
Is it an invalid YAML syntax? Should I update it or is it a BC break in 3.3?
The text was updated successfully, but these errors were encountered: