Nested URLs for Ember Data's RestAdapter proposal

[amiel]

I’m new to this debate (I’m just trying to help get it working in ember-data), but I think nested resources are much more difficult to handle generically from the client side. It is much simpler to say “when I create a comment, POST to /comments”. If I have an id of a comment, I should be able to just fetch it (/comments/:id), and not need to figure out what comment it belongs to before I can fetch it.

After dealing with this in my own app and trying to figure out how to make it less painful in ember-data, I’d have to say this has far more weight that at first it seems.

@mixonic explains in far more detail (with better arguments) here: Suggested REST API Practices (2013) :: madhatted.com

Also see:

I was being silly to fight Ember-Data on nested URLs, I think

I spent all day yesterday looking at ways to deal with my endpoint API. /users/:user_id/sources/:source_id/items/:item_id makes conceptual sense in the API construction, which I built first. But sources, items, and users all have their own ID space, and while it’s a straightforward has-many relationship straight down the chain, there’s no real reason why I can’t do /users/:id, /sources/:id, and /items/:id instead. I’m starting to sense that there’s a general feeling that nested URLs like that…