How to deal with partial resources

[skoging]

As far as I can see, there isn't currently a robust way to handle requests that return partial resources.

In particular, I want to do a list request where I only want to request a couple of the fields of a resource. Then I will request the complete resource when I need it. This works as expected, where the detailed resource replaces the existing partial resource. The problem is that if I reverse the order of these requests.
Say I'm at a detail page, and navigate back to the list page, if the list request is stale or not in the cache, the partial resources that are fetched will replace any complete resource that is already cached.

Are there any suggestions for how to deal with this? Or plans for improvements that will make this use case possible?

[skoging]

I did dome more testing, and it appears lodash merge deals with class instances differently to plain objects.

https://runkit.com/skoging/5c866ccaa0922f0014c0835e

In particular, classes are not recursively merged, so undefined fields are not skipped.

[skoging]

I've just been busy lately. I'll take another pass on this in the next couple days.

…

On Wed, Mar 13, 2019 at 5:15 PM Nathaniel Tucker ***@***.***> wrote: Are you looking for more feedback, or just busy? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFyGWSuwH00Bx9SwgMZeVdGAF_zL41EMks5vWSQ7gaJpZM4bogqb> .

[ntucker]

#10