tech(observation): Enqueue modifications in ObservationRegistry #54

pjechris · 2023-08-07T16:56:15Z

⚽️ Description

Instead of post changes one by one, now modifications are enqueued and posted once store/update is finished.

💥 Post is asynchronous. This was already the case but now it's also the case for the first value
💥 Now both EntityObserver Publisher and regular EntityObserver post the first value
Tests were updated to check we don't trigger too many changes
Tests were updated to make sure we trigger changes for all stored/updated types
Changes are computed at the time of postChanges is called. Any subsequent changes will be posted in next call

…terd at the time of the call

… type

pjechris added 10 commits July 28, 2023 17:04

[store] enqueue changes

fe7262a

[tests] add test to check enqueued entities

b20abf3

[tests] add test to check IdentityMap Publisher

e462690

[entity] changed onChange implementation

349e9ea

[registry] don't keep strong ref to nodes and post to observers regis…

8ca4763

…terd at the time of the call

[registry] fixed mismatch btw postChanges and observer expected value…

e91763e

… type

[registry] add hasPendingChange method

4d3d0f1

[publisher] fixed publisher sending value twice the 1st time

b2481ee

[tests] fix pendingChanges test

efa0de5

[store] refactor queue post

d3e87f9

pjechris added breaking change Code that add significant changes tech labels Aug 7, 2023

pjechris merged commit 8779ade into main Aug 8, 2023
2 checks passed

pjechris deleted the feat/observer-enqueue branch August 8, 2023 07:58