-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Fragment] Move configuration to PHP #37211
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
[Fragment] Move configuration to PHP #37211
Conversation
Q | A |
---|---|
Branch? | master |
Bug fix? | no |
New feature? | no |
Deprecations? | no |
Tickets | Ref #37186 |
License | MIT |
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 looks correct to me!
I only have two minor questions:
(1) Should we standardize the order of PHP calls? In the original XML file, the tag was added before the args, so in PHP is the same:
->tag('kernel.event_subscriber')
->args([
service('uri_signer'),
param('fragment.path'),
])
But maybe we should put args first always?
->args([
service('uri_signer'),
param('fragment.path'),
])
->tag('kernel.event_subscriber')
(2) We should probably inline some args()
calls because their service list is short enough:
// Before
->args([
service('uri_signer'),
param('fragment.path'),
])
// After
->args([service('uri_signer'), param('fragment.path')])
tags are added after the args (and calls) in the other PRs. So I think this should be changed for consistency here. |
@Tobion , so order is ->args()
->call()
->tag() Right ? |
If someone can help, i don't know how to fix the test 😢 |
@idetox don't worry about it, it's a random failure. I've re-run the jobs to see if it happens now. |
Can you squash your commits please? |
Thank you @idetox. |