relations included

[joacub]

there is a little gap in the logic, what about when you are requesting something like this,

query : {
include: [UserData]
}

the include is treat in the backend doing the association and in the client that reference to the same item id so it get updated and sometimes removed, the id must be composed by the relations included so it does not get updated or deleted by other queries without this association included
.

good project by the way. I like.

[KidkArolis]

I see, I guess Figbird is not currently "include" aware (it's not a standard Feathers feature), wonder if we this would be possible with some kind of API for intercepting responses/events and modifying how it gets mapped to the cache. Hm.

[joacub]

What I’m doing to fix this is doing a incremental entities update by merging them in deep. So entity’s gets hydrated when has more data

[joacub]

Btw this only harkens when using get . Find gets cached by id