Dispatcher initialization at a 5000ms time frame

[VincentVanTongeren]

What is the reasoning behind the 5000ms time frame for adding a store?

In dispatcher.ts there is the following line:
export const $$addStore = new ReplaySubject(50, 5000);

In my use case, I have a custom storage set up with persist state. GetItem is an observable that internally needs to wait until there is a connection with another system in order to retrieve the persisted initial data. This requires a manual action and since the timer starts ticking automatically, more often than not, this 5000ms window passes.

In my local environment, I have removed the 5000ms restriction to the default restriction (Infinity) and now it works like a charm. I would like to know if the 5000ms is there for a very important reason and if I can remove the restriction. The most ideal solution would be to be able to override this parameter or supply my own subject.

[NetanelBasal]

I'm not sure how this internal function is related to what you're trying to do.

[VincentVanTongerenTopicus]

Thanks for thinking along with us. As far as I understand, that would require a new hook in akita to process retrieved persisted data, since the encrypted data cannot be mapped to the stores contents directly. I can only supply a method that retrieves data somehow and I assume that the getItem interface on PersistStateStorage expects finalized data that can be used at once.

[NetanelBasal]

Hmmm what about something like:

@Injectable()
export class TodosQuery extends QueryEntity<TodosState> {
  constructor(protected store: TodosStore) {
    super(store);
  }

  select() {
    return super.select().pipe(filter(state => state.decrypted));
  }
}

[NetanelBasal]

Check this https://stackblitz.com/edit/angular-ivy-fyxaha?file=src%2Fapp%2Fstore%2Ftodos.query.ts

[VincentVanTongerenTopicus]

That might work, I will explore this in our project!

Thanks for your time and thoughts!

[MarekCikos]

Hello, I have a similar problem.

In dispatcher.ts there is the following line:
export const $$addStore = new ReplaySubject(50, 5000);

and in persistState.ts there is the following piece of code in method persistState():

subscriptions.push(
	$$addStore.subscribe((storeName) => {
                // ...
		// ...some piece of unimportant code
                // ...
                // creating a subscription to changes in the store
		subscribe(storeName, path);
	})
);

Questions:

1. does this mean that if an application has for example 54 stores, a subscription to changes will be created only for the last 50 stores (because of ReplaySubject capacity of 50) and changes for the first 4 stores will not be stored in the storage (localStorage/DB)?
2. Does this mean that if there is a time at least 5 seconds between the store constructor call and the persistState method call, $$addStore.subscribe will have no values to subscribe and therefore no values will be stored in the storage (localStorage/DB)?

In my use case I have the login page where the user needs to log in. During login page opening, all stores are created. Then the user can log in and this action can take from seconds to minutes or hours (opened application in login page). After the user is logged in, the code calls persistState method and provides custom storage (DB Storage) to save all user's store values to database. After the logout, the storage object from persistState method is destroyed (storage.destroy()) and login page appears again for another user to log in. Every user has different stored values and these values are sensitive (store must be clean after every logout and before every login).

My problem was that if the login page was opened for 5 seconds or more, the user's store values were not updating after the login because the subscription was not created (see code above).

I solved this problem in a way that i cloned akita library and rewrote export const $$addStore = new ReplaySubject(50, 5000); to export const $$addStore = new ReplaySubject(); This resolved all my problems. Is there a way to configure these values or can be this feature added to any future releases? Or is there any other way to resolve this kind of problem (long time window between the store creation and the persistState method call)?

Thank you for your advice @NetanelBasal
Marek