Any recommended workaround for embedding resources in Create/Update requests

Hi,

I've read up a lot of information about how 'embedded' / 'nested' resources are scheduled for v1.1 of the json-api but I was just wondering if anyone using jsonapi-resources has an interim solution, for de-serializing create/update requests where I can create / update a set of related entities. In the case of the create they wouldn't have client generated ids. I'm just hoping to create them as Rails nested resources.

Is there possibly a workaround for json-api resources similar to what was created for Active Model Serializers here: https://github.com/json-api/json-api/issues/795#issuecomment-202810800

I'm just trying to create a a few related entries in an atomic request.

For record fetching, I use sideloading.

I'm using Ember-data with the EmbeddedRecordsMixin to include the embedded relationships

Thanks for any suggestions

Das Issue nennt keine Repository-Dateien oder Tests; beginne damit, die Deserialisierung von jsonapi-resources-Anfragen für create/update nachzuverfolgen und den verlinkten Workaround von Active Model Serializers zu vergleichen. Erledigt ist die Aufgabe, wenn ein Weg für die atomare Erstellung und Aktualisierung verwandter Entitäten ohne vom Client generierte IDs etabliert ist.