How to get a nested resource without getting the parent?

[Dylan-Chapman]

Say I want to get the posts for ID user 1, "/users/1/posts". However, I have no need to get the actual user object, "/users/1" first. Is there a built-in way to do this? I didn't have luck trying to run User.find(1).posts().get() for example. Any other way to accomplish this without the unneeded API call?

[robsontenorio]

You can create new instances manually. See on README.

let post = new Post()
post.id = 123

// or just pass as a payload

let post = new Post({id: 123})

// of course you can pass any other params

Then..

// GET /posts/123/comments
let comments = await post.comments().get()

Make sure Post and Comment extends from a BaseModel.

[Dylan-Chapman]

Awesome, thanks! This method seems to work with get but not find as far as I can tell, though? So, modeling off of your example, I have:

const User = new User({id: 1})
const Post = await User.posts().find(2)

This fires "/posts/2" instead of "/users/1/posts/2".

[robsontenorio]

The find() method is suposed to be used with single resources.

For nested resources you should always use get().

As described on README you can use another methods before get() on nested resources.

await user.posts().where('id', 2).get()

[Dylan-Chapman]

Okie dok. Is there some philosophy behind the find() method not being able to be used with nested resources? I thought nested resources with multiple identifiers was a common REST API pattern?

[robsontenorio]

My bad, you are right. I Will look it further. — Robson Tenório Em 4 de jun de 2018, à(s) 17:47, Dylan Chapman <notifications@github.com> escreveu:

…

Okie dok. Is there some philosophy behind the find() method not being able to be used with nested resources? I thought nested resources with multiple identifiers was a common REST API pattern? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[robsontenorio]

@Dylan-Chapman Now you can do this

const User = new User({id: 1})
const Post = await User.posts().find(2)

Just upgrade to 1.1.0. Thanks @vjoao for PR!