You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2019. It is now read-only.
I started using this microframework about a week ago. Works great especially when integrating with a ZF3 framework or resuing existing ZF3 modules.
I wrote a lot of route handlers and got a little lazy at figuring out what the __invoke function should have as arguments. So I wrote a Route Interface definition to ensure compliance with how handlers are invoked.
If you are interested, I forked the project and added RouteInterface.php under the src folder.
I am quite new to GitHub as a contributor and I am not sure about how to do pull requests and such.
Thanks
Eric
The text was updated successfully, but these errors were encountered:
+1 to the idea of an interface. I would name it HandlerInterface personally though instead of RouteInterface. I think the latter would be a bit ambiguous. There is a lot of flexibility to how a handler is registered so it may be good to have a couple different interfaces such as one for invokable classes and another for a predefined, named method in classes.
Hi,
I started using this microframework about a week ago. Works great especially when integrating with a ZF3 framework or resuing existing ZF3 modules.
I wrote a lot of route handlers and got a little lazy at figuring out what the __invoke function should have as arguments. So I wrote a Route Interface definition to ensure compliance with how handlers are invoked.
If you are interested, I forked the project and added RouteInterface.php under the src folder.
I am quite new to GitHub as a contributor and I am not sure about how to do pull requests and such.
Thanks
Eric
The text was updated successfully, but these errors were encountered: