Elf in an Angular application

[davidsidlinger]

First of all, I want to say I'm enthusiastic about this library and the direction is heading. It feels much more natural to configure a store through composable functions rather than the base class approach used in Akita.

I am trying to wrap my head around a couple details while trying it out in an Angular application that currently uses Akita as its Redux store.

It's very appealing to define a repository module that exports the functions to get and set state. I am struggling with finding the correct approach to unit test consumers of this module, though. Is the intent to wrap it all up in a *Repository injectable service and test as we normally would with mocks? That approach seems like it would work but at the same time feels like extra clutter or work and is highly Angular specific. Am I missing something?

My other question is a little more specific to our application. We are creating a PWA where our Redux stores are persisted to local storage for offline functionality. persistState works great and in many ways is far ahead of the all-the-stores persistence found in Akita. What I'm trying to figure out is how to handle updates to state in multiple tabs. In our existing code, we're using localforage to create a cross-tab observable to apply the snapshot saved to everything at once. I'm not finding a way to do this with the per-store persistence found in Elf. Is there a recipe for this yet?

[davidsidlinger]

I found the answer to my first question through the power of … reading. :) It was in the README.

I will mark this as answered and open a discussion specifically around cross-instance persistence.

[NetanelBasal]

👍