An interesting design question arrises around nested resources. Google in this doc buys into deep nested structures, e.g. `//calendar.googleapis.com/users/john smith/events/123` (from [1]).
I think this pattern is unambiguously sensible when the child objects are strictly scoped under the parent.
But it's less clear how to represent resources that are shared between multiple parents; for example, what if event 123 can be referenced under another user's API resource as well? If we permit `//calendar.googleapis.com/users/bob/events/123`, now we have multiple URLs referring to the same object, and things can get quite tricky in the implementation.
Django Rest Framework strongly discourages (and makes it quite hard to implement) nested resources, FWIW.
I've found that a policy of only permitting one level of nesting seems to be a good balance for shared objects, e.g.
`//calendar.googleapis.com/users/john smith/events/` returns:
```
[
{ url: "/events/123"},
...
]
```
Interested to know how others have solved this problem.
[1]: https://cloud.google.com/apis/design/resource_names
I think this pattern is unambiguously sensible when the child objects are strictly scoped under the parent.
But it's less clear how to represent resources that are shared between multiple parents; for example, what if event 123 can be referenced under another user's API resource as well? If we permit `//calendar.googleapis.com/users/bob/events/123`, now we have multiple URLs referring to the same object, and things can get quite tricky in the implementation.
Django Rest Framework strongly discourages (and makes it quite hard to implement) nested resources, FWIW.
I've found that a policy of only permitting one level of nesting seems to be a good balance for shared objects, e.g.
`//calendar.googleapis.com/users/john smith/events/` returns:
``` [ { url: "/events/123"}, ... ] ```
Interested to know how others have solved this problem.
[1]: https://cloud.google.com/apis/design/resource_names