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
I was looking up a way to use the powerful Symfony router (specially yaml defined routes with catching for PROD) with Silex and I've found your repository. I very much like your ChainedRouter which adds, on top of the Silex router the Symfony one.
As I understand it, this repository is here in order to use the providers outside the Brick project. But unfortunatelly the Rotuing provider is tightly coupled with the Brick repository where the Brick\Routing namespace lives.
Is there any chance to move the Brick\Routing namespace from flint\Brick to this repository? I am willing to create a PR but I won't start if you won't go this path (and I would understand completely, is your project after all).
Of course I can pull in the flint/Brick package, but as for the existence of this one, I though it is possible to extract more in order to truly reuse your fantastic providers.
PS: The same issue happens with the Exception Provider which is coupled with the Controller\ ExceptionController class
The text was updated successfully, but these errors were encountered:
I was looking up a way to use the powerful Symfony router (specially yaml defined routes with catching for PROD) with Silex and I've found your repository. I very much like your ChainedRouter which adds, on top of the Silex router the Symfony one.
As I understand it, this repository is here in order to use the providers outside the Brick project. But unfortunatelly the Rotuing provider is tightly coupled with the Brick repository where the Brick\Routing namespace lives.
Is there any chance to move the Brick\Routing namespace from flint\Brick to this repository? I am willing to create a PR but I won't start if you won't go this path (and I would understand completely, is your project after all).
Of course I can pull in the flint/Brick package, but as for the existence of this one, I though it is possible to extract more in order to truly reuse your fantastic providers.
PS: The same issue happens with the Exception Provider which is coupled with the Controller\ ExceptionController class
The text was updated successfully, but these errors were encountered: