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
It would be nice to have some sort of "sub resource".
The idea is to fill the need of /user/5/posts
This resource should use the posts models, but have it's own routes. The routes could be /user/#, or whatever other prefix is taken.
This ticket should be tied into #1 somehow.
When #1 splits routes into their own file separate of the core description, it could receive a label of some sort, and the sub route chooses a different label of routes.
Maybe this could also be tied into #8, and the private label could handle that.
The text was updated successfully, but these errors were encountered:
It would be nice to have some sort of "sub resource".
The idea is to fill the need of /user/5/posts
This resource should use the posts models, but have it's own routes. The routes could be /user/#, or whatever other prefix is taken.
This ticket should be tied into #1 somehow.
When #1 splits routes into their own file separate of the core description, it could receive a label of some sort, and the sub route chooses a different label of routes.
Maybe this could also be tied into #8, and the private label could handle that.
The text was updated successfully, but these errors were encountered: