The server sends a lot of data nested (like author objects) instead of just the id.
Only sending the id would make the total response size smaller as the client would then cache these objects.
The server sends a lot of data nested (like author objects) instead of just the id.
Only sending the id would make the total response size smaller as the client would then cache these objects.
Here is the expected result on the API:
Until this is implemented, the Java lib will ignore everything that is not an ID in the above-mentioned requests. This way, the implementation of this task will be very fast.
Until then though, the lib will be getting a lot of unneeded data (I will not implement the reading of nested objects with cache verification since it's going to get deprecated in the near future anyway).
Currently there is no way to get a specific draft's data. Before this, the solution was to get the list of drafts with their data nested, but this is going to be removed.
An API endpoint at GET /areas/ID/drafts/ID/ would be necessary to update the local cache for a draft.
I'd like to keep this one, because it removes unneeded nesting in serializers and therefore having data in multiple places