[DependencyInjection][FrameworkBundle] Fix precedence of App\Kernel
alias and ignore container.excluded
tag on synthetic services
#60392
+33
−12
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.
Autoconfiguration cannot make a service abstract so I'm removing the related calls, they're confusing.
Then, I'm moving the definition of the
App\Kernel
alias after loadingservices.yaml
, so that the alias overrides the discovered corresponding class.And I make instance-of-conditionals ignore
container.excluded
tags on synthetic services. An alternative could be to check if the class implementsKernelInterface
like proposed in #60191 (comment) but I think the rule I'm proposing here is more generic.