-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Properly handle optional tag attributes for !tagged_iterator #32604
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
Conversation
(tests fail) |
When using the array syntax
@nicolas-grekas I wrote the test apparently for Symfony 4.4+, not 4.2. Should I send a separate PR for 4.4+, where I just rename |
Should it be merged in 4.2 or 4.3? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(4.3)
Thank you @apfelbox. |
…or (apfelbox) This PR was merged into the 4.3 branch. Discussion ---------- Properly handle optional tag attributes for !tagged_iterator | Q | A | ------------- | --- | Branch? | 4.3 | Bug fix? | yes | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? |no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | #32603 | License | MIT | Doc PR | — Properly handles all optional array keys when using `!tagged_iterator` in YAML service definitions. This fixes a regression and adds a test case preventing it from coming up again Commits ------- d1c6580 Properly handle optional tag attributes for !tagged_iterator
@nicolas-grekas should I prepare a follow up PR for 4.4, or will you fix the test when merging up? |
It's already merged up :) |
Properly handles all optional array keys when using
!tagged_iterator
in YAML service definitions.This fixes a regression and adds a test case preventing it from coming up again