It includes the requested path, indicating that there is something beyond there and giving its optimized path ripe for model.deref(). This is in line with Falcors philosophy of only returning what the client asked for.
This change would be most useful for a controller handing out dereferenced models to views.
One can imagine a generic list view that (itself been given a model dereferenced to an array) creating child views with models dereferenced to individual array items.
Currently it is impossible to dereference any item without knowledge of some leaf value within (or beyond) the item, preventing the creation of such truly generic list view.
I don't see this change would break something, but I might be wrong.
An example to illustrate.
There's no mention of the path I asked for (implying it doesn't exist?) Instead I propose to make the response be
It includes the requested path, indicating that there is something beyond there and giving its optimized path ripe for
model.deref()
. This is in line with Falcors philosophy of only returning what the client asked for.This change would be most useful for a controller handing out dereferenced models to views. One can imagine a generic list view that (itself been given a model dereferenced to an array) creating child views with models dereferenced to individual array items. Currently it is impossible to dereference any item without knowledge of some leaf value within (or beyond) the item, preventing the creation of such truly generic list view.
I don't see this change would break something, but I might be wrong.