Fetch only autosave.modifiedDate object instead of the whole meta object

[malinajirka]

The introduction of the List Management component changed the way we fetch posts from the server. We basically first fetch just list of ids, modifiedDates and statuses -> if the PostModel in our local database has the same status and modified date, we don't fetch its detailed data. This approach saves tons of data and is also more performant.

However, we've started fetching the whole "meta" object here - this change was introduced in this PR as we didn't come up with a better solution.

Ideal fix for this issue is to add support for requesting specific nested fields to the API -> we'd request just "meta.data.autosave.modified" instead of the whole meta object.

cc @shiki @maxme

[shiki]

Sounds good to me. @malinajirka, have you measured how big the meta objects can be?

[malinajirka]

The difference is significant. This is just an example + if you take into account the autosave.content can be huge, I believe this ticket should have at least a medium priority.

vs

[shiki]

Thank you. I agree. That is significant.

[maxme]

Sounds good to me. I had a look at the API doc and I'm not sure how this is doable.

I tried meta=data.autosave.modified and meta=autosave.modified but it doesn't work.

[malinajirka]

Yes, sorry. I should have been more explicit. This is not supported on the API at the moment. I created this ticket so we don't forget about it and propose the change to the API team.

[malinajirka]

The api change request is being discussed here - p3hLNG-14E-p2.

[shiki]

Fixed in #1379