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
This requires tests to be written against more than just the routing code. The path should result in a 404 if and only if there is excess routing information after it has already been resolved to a Controller/Action and the action method is not a __call method and the action method does not take $opts.
In the case of a __call method, it is the responsibility of the ResourceController to determine if there is excess routing information based on the method that gets called. This almost calls for a refactoring of the routing logic to include some in individual controllers. (ugh!)
In the case of action methods that take $opts, it is their responsibility to validate the $opts.
For instance
/home/
and/home/index
should both be valid and should be equivalent, but/home/index/does/not/exist
should not be a valid pathThe text was updated successfully, but these errors were encountered: