tech(observer): Use a registry to register observers #53

pjechris · 2023-07-28T12:51:29Z

⚽️ Description

This is a first step in collapsing observe changes by introducing a central type to handle them: ObserverRegistry.

On long term this should allow to better manage observations including collapsing like just said.

For now it does nothing more than what was done before.

Related to #48

Replace EntityObserver/AliasObserver internal implementations with ObserverRegistry
Trigger ObserverRegistry every time a node value changes
Added API to collapse notifications. But for now stick to a postNotification for every change.

…or now

pjechris added 14 commits July 25, 2023 18:39

[observer] introduce registry

c10ce12

[registry] use less costly id generation

a2127a4

[registry] use node hash as key

6cc678c

[node] fix odd hash implementation 🤔

b435245

[registry] remove Unmanaged

8a6fe16

[registry] add notification enqueuing system

69b6c5f

[store] post notifications

81b9860

[node] add onChange closure

0497000

[observer] use registry inside EntityObserver

b58c474

[observer] use registry inside AliasObserver

30f2bd1

[tests] move EntityObserverTests tests to ObserverRegistry

8fb9591

[store] revert to old notification: don't use pending notifications f…

43569e0

…or now

[tests] fixed tests

12dc287

[tests] add tests on registry

59a123c

pjechris added the tech label Jul 28, 2023

pjechris merged commit 5a87c9e into main Jul 28, 2023
2 checks passed

pjechris deleted the tech/observer-registry branch July 28, 2023 13:02