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 Jan 8, 2020. It is now read-only.
It says that i tCould not match a controller. However, changing the controller part in the route to something like 'ember create eController ' works. I suppose "controller" should not be a reserved keyword for routes.
The text was updated successfully, but these errors were encountered:
This doesn't work because the Simple route will turn the controller literal (in your route definition) into a RouteMatch parameter with value true. This value will in turn override the default parameter value of 'ZfrEmber\Controller\CodeGenerator'.
In essence you will attempt to dispatch to a controller with service name true, which doesn't exist, hence the 'Could not match a controller` error message.
So as it stands, you cannot have a literal controller in your route definition and dispatch to an arbitrarily named controller. One way to resolve this could be (untested) to use a mandatory named alternative with one alternative in your route definition 'ember create (controller):altGroup <controllerName>'. That doesn't work.
I have the following route in the console router:
It says that i tCould not match a controller. However, changing the controller part in the route to something like 'ember create eController ' works. I suppose "controller" should not be a reserved keyword for routes.
The text was updated successfully, but these errors were encountered: