Throw Exception when controller for routing configuration does not exists
When developing Flow applications and creating the routing configuration it´s a problem to find errors in the configuration when a simple typo in the controller is hidden by ignoring the absence of the named contoller in the Routing.yaml.
It would be nice to receive an exception in case the mentioned controller in the Routing.yaml does not exists.
Updated by Bastian Waidelich about 8 years ago
- Status changed from New to Needs Feedback
could you please add more details (e.g. your routing setup and the exception you get/expect)?
In development context you should get an exception like the following if a controller/package does not exist:
No controller could be resolved which would match your request. Package key: "foo.bar", controller name: "baz"