Links and meta improvements#160
Links and meta improvements#160pangratz wants to merge 10 commits intoemberjs:masterfrom pangratz:ember-data-links-meta-improvements
Conversation
|
I started working on a proof of concept https://github.com/pangratz/ember-data-meta-links-improvements. |
- replace RecordArrayReference in favor of DocumentReference - outline different locations of meta - add code sample for different meta of a resource - add unresolved question for additional `extractMeta` hook on `RESTSerializer`
|
I gave this more thought and after realizing that JSON-API allows different locations for meta on a JSON-API document (especially relevant for a single resource), I've updated this RFC:
|
|
|
||
| Book.reopenClass({ | ||
|
|
||
| didReceiveData(recordRef) { |
There was a problem hiding this comment.
FWIW, this is very similar to the way we are handling this case in our hacked-up version of Ember Data we are currently using to address this problems. +1 to the approach from our POV.
|
Is there anything we can do to move this along? I can't use Ember Data until there's link-based relationship saving :( |
|
Same here, if there's any grunt work that first time contributor can do to help, I'd be happy to lend a hand |
|
summoning @wecc |
|
For what it's worth, my company is in the same boat. Until Ember Data fully supports the JSONAPI spec, including using related links for operations other than GET, we can't recommend Ember's full scale use. We have data sets in the thousands so sending all the elements of a And we are willing to help and contribute as well. |
|
This is a fundamental dealbreaker for Ember Data, and it's coming up on 2 years since I first ran into this issue. The roadblock doesn't seem to be in implementation but just having an RFC approved. Why can't we get a decision from the core team on this? |
|
Judging by the consensus here people are happy to wait indefinitely. |
|
6 months further on, still no response from the core team. If there is some protocol or path to moving this forward that I'm not aware of, someone please inform me. |
|
FYI: #332 |
|
FYI: #332 |
|
@benedikt-d confirm that #332 supercedes this by solving the base set of cases. Closing. |
9 participants
Rendered
cc @tchak @wecc
This RFC was born in Greece during the Ember Thalassa event, sponsored by bookingsync.com.