Is it acceptable to use Elf for Component State in Angular?

[clark-stevenson]

Forgive me if it's a silly question, I am new 😭

I was considering doing something like this:

@Injectable()
export class MyStoreService implements OnDestroy {
      
      store = createStore();
      
      ngOnDestroy(): void {
           this.store.destroy();
      }
      
}

And using it in my Component like this:

@Component({
  selector: 'app-my-component',
  providers: [MyStoreService],
  changeDetection: ChangeDetectionStrategy.OnPush,
})
export class MyComponent  {
     
     constructor(public readonly myService: MyStoreService){
     
     }

}

I assumed it was OK but I ended up doing a little digging and I ran into this comment

Note that destroy only removes the store from the global stores' repo; it doesn't destroy the actual instance.

I don't actually know for sure in depth, but due to getRepository() there is obviously something bigger happening and ultimately it boils down to seeking confirmation that in the end, when my component is destroyed, it's service is destroyed and therefor the store is destroyed and if that doesn't happen then that is the part I am missing.

Either that or I am abusing Elf entirely 😁

PS Thanks for Elf! It's actually pretty beautiful to work with in my limited tinkering so far.

[NetanelBasal]

This is the way. You're creating the store inside the class so it's OK.