Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Contracts] Fix setting $container before calling parent::setContainer in ServiceSubscriberTrait#49441
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
carsonbot commentedFeb 18, 2023
Hey! I see that this is your first PR. That is great! Welcome! Symfony has acontribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
8b7fcb2 to1c2ab9dCompare
nicolas-grekas left a comment
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.
Makes sense to me.
Uh oh!
There was an error while loading.Please reload this page.
…r in ServiceSubscriberTrait
7a53a1a tobccb074Comparenicolas-grekas commentedFeb 21, 2023
Thank you@edsrzf. |
This changes the
setContainermethod ofServiceSubscriberTraitso that it callsparent::setContainerfirst, before updating$this->container. This is so that the parent method can work correctly if it relies on the old container value.This is particularly relevant for
AbstractController, since it returns the old container value. When used withServiceSubscriberTrait, it returned thenew container rather than the old one. This, in turn, caused incorrect behavior in framework bundle'sControllerResolver, as described in#49382.