(07-07-2016, 10:55 PM)orionstar Wrote: @kilishan You mentioned that there will be an event system... A default beforeController/afterController events are not enough? The controller and actions name can be passed by arguments. After that the user can do whatever wants with the data.
It's entirely possible, but currently there's no simple way to specify
which endpoints the event would affect. It would leave each event doing a bunch of checks, which would get gnarly quick. Additionally, there's no way to stop the controller action from an event, which is a big part of why you'd want to run before filters, anyway. I'm not 100% that returning a redirect from a hook would do anything at this point, without trying it, though I believe it would. So, events come close, but not 100%.
