Yes, imho this should be a good place to start, seeing also that zend is adopting it, this could be a good reference. I'll look better the package tomorrow anyway.
We should think a way to abstract the Route and RouteResult value objects. On Thursday, November 17, 2016 at 11:07:53 PM UTC+1, Matthew Weier O'Phinney wrote: > > On Thu, Nov 17, 2016 at 3:12 PM, Damiano Petrungaro > <damianop...@gmail.com <javascript:>> wrote: > > I'm doing a microframework (for educational purposes), with the goal of > use > > in the core only methods derived from the PSR interfaces, so as to give > > maximum flexibility and not be bound to an implementation rather than > > another. > > > > Now i'm thinking about a routing system, and i'm wondered, how a so > crucial > > component to web applications (used by all the frameworks) haven't a > > standard. > > > > What do you think to propose it as a possible PSR? > > With Expressive, we've actually started down this direction already, > and Michael has been urging me to submit our ideas around this as well > as templating as potential recommendations. > > Maybe take a look at zend-expressive-router and its RouterInterface, > Route class, and RouteResult as a place to start? > (https://github.com/zendframework/zend-expressive-router) > > I'm certainly willing to discuss! > > > -- > Matthew Weier O'Phinney > mweiero...@gmail.com <javascript:> > https://mwop.net/ > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/19b3ac35-806d-4b1c-b17e-71f525c5c983%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
