Skip to content
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

Store notifications should accumulate operations and not override them #286

Open
boxdot opened this issue Jan 10, 2025 · 0 comments
Open

Comments

@boxdot
Copy link
Collaborator

boxdot commented Jan 10, 2025

Originally posted by @raphaelrobert in #282 (comment)

Currently, when notifying a change about a specific entity, if there is already another change, it will be overridden by the new change. E.g. if entity X is notified about being added, and then being updated, StoreOperation::Add will be replaced by StoreOperation::Update.

In the previous example, this is problem because observers will never see that an entity was added.

A simple solution for that is to introduce an EnumSet and store all operations that were applied to an entity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant