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
Although having a one level deep controller stack is a clean convention, and a limitation that helps for a cleaner route table, there are cases (especially in plugins) where some controller needs to be nested.
For example, the [twitter] module may have links that belong under the api namespace. So a request to the twitter api may look like:
/api/twitter/[request/uri]
The controller that accepts those requests needs to live either in an api folder or be named api-twitter.js.
Either convention should have the same effect.
The text was updated successfully, but these errors were encountered:
Although having a one level deep controller stack is a clean convention, and a limitation that helps for a cleaner route table, there are cases (especially in plugins) where some controller needs to be nested.
For example, the [twitter] module may have links that belong under the
api
namespace. So a request to the twitter api may look like:The controller that accepts those requests needs to live either in an
api
folder or be namedapi-twitter.js
.Either convention should have the same effect.
The text was updated successfully, but these errors were encountered: