support providing array of ResourceIdentifier for apply and rollback

[abdulhaq-e]

support providing array of ResourceIdentifier for apply and rollback

[abdulhaq-e]

In addition, rather than searching everything for resources to update, maybe it's better if a new part of the store holds the resources that need to be applied.

So the moment a resource is marked as CREATED/UPDATED/DELETED then the identifier of that resource is put in the store which can then be used by apply instead of searching. What do you think?

[remmeier]

yes seems perfectly right, the set of ids of resources that are updated together should be stored in store as well. But I think this is something very application specific and ngrx-json-api should not attempt to solve that for an application.

In general I like the current data model. It is simple, normalized. I can select a resource and get all the information including original remote state, update state, etc. All that makes it easy to use and explain. So I think that should remain unchanged in the context of this ticket.

From a performance perspective, apply is called quite rarely. The looping a few dozen to thousand resources is negligible.

so to conclude, I think, just those array of ResourceIdentifier and a set of inclusions should be sufficient. But the documentation should state how to make use of that (meaning write an effect or something than then triggers the apply action with ids fetched from elsewhere in the application-specific part of the store)

[remmeier]

introduced a "ids" and "include" parameter to control which parts of the store should be applied to backend.