Questions about future maintainability

[jameshulse]

Hi everyone. First of all, great idea for a libary, and the implementation looks very useful. We hand rolled a similar 'Action' framework in the current app I am building because we had the same feeling about how Laravel applications were factored.

Before we port to using this library I have a few questions for those that have used the framework for a while in anger:

1. Has the promise of future maintainability been maintained in your experience?
2. Any pitfalls we should be aware of when designing actions?
3. I have worries that calling actions from actions would lead to a messy web of logic. How has this been in practice?
4. Has it been useful to separate the concept of 'user actions' (those initiated by the user on the frontend), and 'system actions' - those that happen because of other side effects or outside conditions.

Thanks!