-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Bring back Partial Upsert #1019
Comments
Also noticed, that the generated schematics code produces incorrect code, where the actions receive an |
Partial entities in the store are messy. You have updateOne & updateMany https://github.com/ngrx/platform/blob/master/modules/entity/src/sorted_state_adapter.ts#L178-L189 |
@MattiJarvinen-BA you might be right, but currently, using the code as they "suggest it" (via |
@gioragutt #1042 keeps the generated code aligned. |
Hi, |
@capaneus Could you please explain why update doesn't work for you? Can the user update items that aren't in the store in the first place? |
Can this please be re-opened? My use case; I use NGRX Store 5.5 to track partial updates for my entities that are batched together before doing a bulk partial update to Firestore. This is a cost mitigation strategy to batch the partial saves in the Store to reduce the number of writes sent to Firestore each time. A more managed debounce so to speak. The system worked quite well. With NGRX 6 upsertOne no longer having support for partial entities... I've lost the API to add a "new" partial change to the store. |
I'm submitting a...
What is the current behavior?
Upsert/UpsertMany in version 6 only supports a fully qualified entity. This doesn't allow for a partial update of the entity with upsert.
Expected behavior:
The text was updated successfully, but these errors were encountered: