Open gecBurton opened 4 years ago
im not 100% sure these are needed tbh... and they are at direct odds with json-api.
my feeling as that these are a very-nice-to-have option. Experimenting with the fhir spec reveals all sorts of hidden horrors re: POST/PUT conflicts... maybe one for 1.0.0
I don't think they are necessarily at odds with json-api if the nested objects are within the resource's attributes rather than relationships
these aren't actually supported by DRF out-of-the-box:
so its not unreasonable to just warn about these, or perhaps auto-generate a
TODO
commentIt could be an optional feature, with the added dependency of https://github.com/beda-software/drf-writable-nested