Task #45430

Throw Exception when controller for routing configuration does not exists

Added by Sören Rohweder about 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Category:
MVC - Routing
Target version:
-
Start date:
2013-02-13
Due date:
% Done:

0%

Estimated time:
Sprint:
PHP Version:
Has patch:
No
Complexity:

Description

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.

#1

Updated by Bastian Waidelich about 8 years ago

  • Status changed from New to Needs Feedback

Hi Sören,

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" 

#2

Updated by Bastian Waidelich over 7 years ago

  • Category set to MVC - Routing
  • Status changed from Needs Feedback to Closed
  • Assignee set to Bastian Waidelich

Closing due to missing feedback. Feel free to comment/re-open

Also available in: Atom PDF