Package dependencies
Permalink
We've had so many problems in the past with package dependencies. on_start methods called from two packages, one registers a permission key, the other uses it before it's registered and so on. Here's a more detailed examplehttps://github.com/mkly/Data/issues/28...
I always believed and still believe, that concrete5 needs a proper way to specify package dependencies or at least a package order. The latter wouldn't be elegant, but it would at least make it possible to get things working without rewriting code and updating the database.
I always believed and still believe, that concrete5 needs a proper way to specify package dependencies or at least a package order. The latter wouldn't be elegant, but it would at least make it possible to get things working without rewriting code and updating the database.
I think event handler sequences can be more granular, even within a single package. At least in theory..
Take a look at the symfony2 event dispatcher framework. It's what our new event system is based on. It has priority , propagation, and I'm confident events will bubble up in ways they never used
To , and do so properly
To , and do so properly
http://symfony.com/doc/current/components/event_dispatcher/introduction.html
Is package dependency the same issue as event handler sequence? Would solving package dependency also solve event handler sequence?