You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be cool to make the management of entity data (collections of data: e.g. Products, Todos) more straight forward in MiniRx.
Currently the immutable updates of entities require quite some boilerplate code.
MiniRx has two APIs to manage state... both need to be able to manage entities and if possible many entities in one feature state.
Redux API: NgRx entitiy adapter could be a good fit in general
FeatureStore, ComponentStore API: the entity adapter could be used there as well
Maybe a new thing: Entity Feature Store: extends Feature Store but sets up an entityAdapter internally. Here we would just manage one entity per Entity Feature Store
Challenge:
Investigate existing entity state management solutions
Add support for entity management in the Redux and the FeatureStore/ComponentStore API
Create EntityFeatureStore: manage (probably) just one entity but with a minimum of boilerplate
Notes
API
Regarding the naming of functions which update entity state: Most probably we should use similar/identical names like NgRx entityAdapter, Akita EntityStore or Elf. These names are known by developers.
New lib?
Should "MiniRx Entity" be part of the mini-rx-store lib or should it be a dedicated lib? Or is maybe a second entry point in mini-rx-store good enough (for tree-shaking)?
The text was updated successfully, but these errors were encountered:
It would be cool to make the management of entity data (collections of data: e.g. Products, Todos) more straight forward in MiniRx.
Currently the immutable updates of entities require quite some boilerplate code.
Existing solutions:
MiniRx Entity state:
MiniRx has two APIs to manage state... both need to be able to manage entities and if possible many entities in one feature state.
Redux
API: NgRx entitiy adapter could be a good fit in generalFeatureStore
,ComponentStore
API: the entity adapter could be used there as wellMaybe a new thing: Entity Feature Store: extends Feature Store but sets up an entityAdapter internally. Here we would just manage one entity per Entity Feature StoreChallenge:
Create EntityFeatureStore: manage (probably) just one entity but with a minimum of boilerplateNotes
API
Regarding the naming of functions which update entity state: Most probably we should use similar/identical names like NgRx entityAdapter, Akita EntityStore or Elf. These names are known by developers.
New lib?Should "MiniRx Entity" be part of the mini-rx-store lib or should it be a dedicated lib? Or is maybe a second entry point in mini-rx-store good enough (for tree-shaking)?The text was updated successfully, but these errors were encountered: