[Contracts] Fix setting $container before calling parent::setContainer in ServiceSubscriberTrait #49441
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution 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 to
1c2ab9d
Compare
…r in ServiceSubscriberTrait
7a53a1a to
bccb074
Compare
|
Thank you @edsrzf. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 the new container rather than the old one. This, in turn, caused incorrect behavior in framework bundle'sControllerResolver, as described in #49382.