Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DependencyInjection] Fix tags on multiple decorated service#28820
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
nicolas-grekas commentedOct 11, 2018
Thanks for working on this! Could you add a test case please? |
shyim commentedOct 11, 2018
I have added a Test which fails, without the Changes. |
nicolas-grekas commentedOct 31, 2018
FYI I pushed-forced an alternative implementation that more precisely focuses on fixing multiple decorations while taking care of not changing the semantics of decorating unrelated aliases. |
shyim commentedOct 31, 2018
Looks fine for me 😊 |
nicolas-grekas commentedOct 31, 2018
Thank you@shyim. |
…ce (Soner Sayakci)This PR was merged into the 3.4 branch.Discussion----------[DependencyInjection] Fix tags on multiple decorated service| Q | A| ------------- | ---| Branch? | 3.4| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets |#28682| License | MIT| Doc PR |After the first run in the loop with the same decorated service it goes only in the hasAlias condition. The tags will be not set here, so the `ResolveTaggedIteratorArgumentPass` will handle only the first decoration.Commits-------90f8df2 [DependencyInjection] Fix tags on multiple decorated service
Uh oh!
There was an error while loading.Please reload this page.
After the first run in the loop with the same decorated service it goes only in the hasAlias condition. The tags will be not set here, so the
ResolveTaggedIteratorArgumentPasswill handle only the first decoration.