Component state

[strigefleur]

Back in Akita I used recipe for local component state to get multiple instances of same state.

What would be the correct implementation in Elf?
I can imagine something with registry but would love to see tailor-made solution from the author.

[NetanelBasal]

There are many ways to do it. Here is one of them:

const { state, config } = createState(
  withProps<{ counter: number }>({ counter: 0 })
);

@Injectable()
export class CounterRepository {
  counter$ = this.store.pipe(select(({ counter }) => counter));

  constructor(private store: Store<StoreDef<typeof state>>) { }
}

export const counterProvider = {
  provide: CounterRepository,
  useFactory() {
    return new CounterRepository(new Store({
      name: `counter-${Math.random().toFixed(3)}`,
      state,
      config,
    }))
  }
}

[EricPoul]

Thanks!
And what do you think about having an ability in ng-cli to create this type of repository template(above example but without onDestroy)? It's nice to have consistency in repositories and there's a high possibility of having components store or pass some data to the initial state given via DI.

[NetanelBasal]

Do you mean creating the state and store inside the repo?

[EricPoul]

Yes, if there's no difference between creating a store out of repo and inside I'd choose the last one. As I see, this type of creating a repo is needed for tests and component stores.

[NetanelBasal]

I don't mind adding it. You're welcome to create a PR.

[EricPoul]

I'll dive into it as soon as be able. It's a more "nice-to-have" feature rather than the "must-have" one.