Fedir Zinchuk
Fedir Zinchuk
Okay, that PR was merged, I close this one. Thanks.
This changes can be done in b/c way, without changing method signatures: - keep `DispatcherAwareInterface` interface - call `$plugin->setDispatcher($dispatcher)` in `PluginHelper::import()`, as it already is - modify `registerListeners()` to throw...
Why it is not belong, what is belong then? Sorry, I do not understand, maybe my knowledge just not enogh. In current case for me no big diference here if...
Hmhm, or you mean that `DispatcherAwareInterface` should be used only when Class triggers some event? Well, then it may have a sense, even though it not an obvious thing. Then...
@SharkyKZ I think we going to use [Lazy Objects](https://www.php.net/manual/en/language.oop5.lazy-objects.php) for plugins, this is where static `getSubscribedEvents()` come in handy. The plugin will be initialized only at time when actual event...
@SharkyKZ If you really want this feature (a possibility to do listeners registration inside the plugin), then it is need a new interface with different method names. Otherwise there is...
Personaly I do not see a reason to have it in core. I mean, to make it work with all core features will require a huge amount of work. But...
**For front-end template:** We should not modify existing template under any circumstances, unless there a bug. It will break many exiting installations that uses this template. There 2 options: -...
UPD. > We should not modify existing template I meant the "template parameters"
That also can work, yes. But for new installations it need to be enabled somehow :)