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
Hmm, I haven't imagined that case.
Are you sure you do use that sort of route in your real world app?
IMO, wildcard routes should basically be avoided to use, since it's hard to trace which action method is actually in use and which action is not. That is totally un-RESTful.
For example, how can you add a new resource that does not respond to #foo in your example routes?
Yup, we use. It's just a helper method that we add in some controllers to make the app ajaxier. Since it's easier to map it with the wildcard, we preferred that way instead of doing one-by-one.
If I have a matcher like this(parametrized):
It says that it's an unused route and as a consequence, it says that my action methods #foo are unreachable.
The text was updated successfully, but these errors were encountered: