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
[5.2] CMSPlugin: deprecation for registerListeners #43395
base: 5.2-dev
Are you sure you want to change the base?
Conversation
make sense for me |
I guess it was not marked as deprecated before becaus we changed the plugins way later. |
Why are you hellbent on neutering plugins again? It's bad enough that you have already poorly implemented event classes while also introducing a number of undocumented B/C breaks without a deprecation period as well as garbage code like #40037 (comment). What benefit do you actually see in forcing plugins to use only |
I would like to see the plugins to be as light as possible (there still a long way to go).
Please more detailed. From quick look on the link, it is probably some bug in implementation, or misuse of the event, which was hiding the bugs in the past.
There a loot more garbage 😄
Perfomance, and better code, did you seen code of But it was set to be this way before, in past, somewhere. From my understanding, it was planed to be similar to Symfony SubscriberInterface. When we drop legacy listeners and use
What is NOT usefull for you? If you have some suggestion to improve it, or alternative ideas, just write it 😉 |
Virtually none of what you said is valid. How exactly does removing support for custom listeners make plugins "as light as possible"? Why did you even mention |
Virtually everything I said is correct, except things that are not correct. Easy.
Removing
Sorry, I mean
Well, because we have all this
Keeping To me, removing |
🤦♂️ Why are you bringing up J3 code again? You still don't understand it's irrelevant? It will be removed when J3 plugin support is dropped, regardless whether
You missed the part where the dispatcher would be passed to the method. But nevermind that,
That doesn't make sense. Not only is it not the right to place to register listeners but it also wouldn't work because the correct dispatcher instance is passed to the plugin after the plugin has been booted. This is correct and expected behavior but it's the way the dispatcher is passed that needs to be fixed.
What kind of argument is this supposed be? |
Whatever, you just complaining about anything.
|
This comment was marked as outdated.
This comment was marked as outdated.
For now, the replacement for deprecated |
Pull Request for Issue # .
Summary of Changes
The PR deprecate
CMSPlugin::registerListeners()
as no longer needed when plugin will implementSubscriberInterface
(I wonder why it was not marked as deprecated before).
Also it removes dispatcher dependency, and set DispatcherAwareInterface to be also removed, this based on @SharkyKZ PR #39387Testing Instructions
Apply PR, and navigate around the site, all should work as before.
The PR requires review from maintainers.
Link to documentations
Please select:
Ping @HLeithner @wilsonge