Numerical keys used with tagged_iterator/tagged_locator reset to 0..n-1 #35953
Labels
Comments
|
Can you check if #35957 doesn't fix the issue already? |
nicolas-grekas
added a commit
that referenced
this issue
Mar 5, 2020
…ityTaggedServiceTrait (nicolas-grekas) This PR was merged into the 4.4 branch. Discussion ---------- [DI] ignore extra tags added by autoconfiguration in PriorityTaggedServiceTrait | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #35916, Fix #35953 | License | MIT | Doc PR | - Commits ------- 09770aa [DI] ignore extra tags added by autoconfiguration in PriorityTaggedServiceTrait
nicolas-grekas
added a commit
that referenced
this issue
Mar 12, 2020
…uzhanin) This PR was submitted for the 5.0 branch but it was merged into the 4.4 branch instead. Discussion ---------- Add test for tagged iterator with numeric index | Q | A | ------------- | --- | Branch? | 5.0 | Bug fix? | no | New feature? | no | Deprecations? | no | License | MIT This is just a new test case for bug in issue #35953 Commits ------- 7aa4e10 Add test for tagged iterator with numeric index
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected: 5.0
Description
When !tagged_iterator have index_by set, and the corresponding tag property values are numeric, the keys actually reset to 0-based index. See repro PR
How to reproduce
See PR #35954
The text was updated successfully, but these errors were encountered: