-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[FrameworkBundle] Fix bad interface hint in AbstractController #24431
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
Does it really make a difference? We have aliases for both interfaces pointing to the same service, don't we? |
I think it's sane to have the type that is closer to the injected implementation in the class itself. |
Instead of changing the interface, I would instead change the implementation to respect the current interface. |
1c29395
to
1a9bf98
Compare
done |
But tests are broken. |
1a9bf98
to
5d29dd0
Compare
Esp. since the FrameworkBundle EngineInterface will be deprecated #21035 |
Thank you @nicolas-grekas. |
…ller (nicolas-grekas) This PR was merged into the 3.3 branch. Discussion ---------- [FrameworkBundle] Fix bad interface hint in AbstractController | Q | A | ------------- | --- | Branch? | 3.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - As spotted by @stof Commits ------- 5d29dd0 [FrameworkBundle] Fix bad interface hint in AbstractController
As spotted by @stof