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
If the router service name was configurable, we wouldn't have to re-implement this factory when the router you want to use is not aliased to RouterInterface::class
WHY would the router not properly aliased to the interface? if that is the case, the application would not pick that router up for routing either and thus would not match?
thats the whole point of how routing works in mezzio:
In my case, I have 2 applications running out of the same code-base, each with a different router instance in the container along with a different set of routes.
If the router service name was configurable, we wouldn't have to re-implement this factory when the router you want to use is not aliased to
RouterInterface::class
mezzio-cors/src/Service/ConfigurationLocatorFactory.php
Line 22 in a61a344
The text was updated successfully, but these errors were encountered: