So I read through the Routing PSR idea and honestly I can't think of it having too many use cases. Why would you ever need to replace a whole router really? But that got me thinking about a different, and much more useful usecase.
While matching the URL to some parameters is usually done once and by the framework itself usually what happens a lot is URL generation within the app. So instead of a full blown routing PSR I propose a simpler one which just provides interfaces for generating URLs from an array of parameters. This would be much more useful immediately since these URL generators could be passed to template renderers to build links, which would make integration of these engines within frameworks easier. This would also mean that some payment processing libraries would be easier to use since they would be able to automatically generate URLs to appropriate controllers etc. -- 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/4ad57eb5-a4e3-4857-826e-26e18e28d286%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
