-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[DependencyInjection] Exclude referencing service (self) in TaggedIteratorArgument
#48685
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
5faa2d4 to
e5570b4
Compare
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.
Uhh thanks for heading back 💪🏻 the good looks good as far as I can say
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.
this does not add support when creating such iterator arguments from Yaml or XML configs
|
Friendly ping @lyrixx |
src/Symfony/Component/DependencyInjection/Compiler/PriorityTaggedServiceTrait.php
Outdated
Show resolved
Hide resolved
|
|
@chalasr the missing part is not the resolution. It is the support for the new argument added in the constructor ( |
e5570b4 to
0cbb176
Compare
|
Got it, thanks. Support added |
0cbb176 to
dd7c6dd
Compare
|
Rebased. Reviews welcome |
src/Symfony/Component/DependencyInjection/Argument/TaggedIteratorArgument.php
Outdated
Show resolved
Hide resolved
src/Symfony/Component/DependencyInjection/Compiler/ResolveTaggedIteratorArgumentPass.php
Outdated
Show resolved
Hide resolved
|
So, this changes the current behavior, but we're confident this won't break anyone, right? |
dd7c6dd to
0a7138d
Compare
TaggedIteratorArgumentTaggedIteratorArgument
0a7138d to
d357973
Compare
|
Yes, at least I am :) |
src/Symfony/Component/DependencyInjection/Compiler/ResolveTaggedIteratorArgumentPass.php
Outdated
Show resolved
Hide resolved
91d624c to
a8afe94
Compare
8000
a8afe94 to
34a24ca
Compare
|
Anything else? :) |
src/Symfony/Component/DependencyInjection/Argument/TaggedIteratorArgument.php
Outdated
Show resolved
Hide resolved
8b5f6fc to
49f0d8a
Compare
49f0d8a to
1cadd46
Compare
|
Thank you @chalasr. |
…(HypeMC) This PR was merged into the 6.3 branch. Discussion ---------- [DependencyInjection] Add `excludeSelf` option to dumpers | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | - | License | MIT | Doc PR | - Followup to #48685. It seems that the `excludeSelf` option was not added to the dumpers or configuration functions. I don't think this was done intentionally, but was an oversight. Commits ------- 09c7581 [DependencyInjection] Add exclude-self option to dumpers
Suggested by @OskarStark in https://twitter.com/OskarStark/status/1594641457226436608?s=20&t=Wbqw_Mu2tMYQ0iouaG8yig.
This PR avoids the need to explicitly indicate to exclude the referencing service when using
#[TaggedIterator]and variants.Before:
After:
I went with no deprecation as I think the breakage potential is close to zero, but happy to reconsider.