How to Manage Long-Lived Resources Without Reconstructing in Effects
What is the best way to model a long living resource that shouldnt be re-constructed on each effect that requires it?
Im working with on the frontend IndexedDB and it is suggested to open a db (
However when i setup a tag+service for manging the database, i noticed that the database is re-opened anytime an effect which requires it's service is ran.
Im working with on the frontend IndexedDB and it is suggested to open a db (
indexedDB.openHowever when i setup a tag+service for manging the database, i noticed that the database is re-opened anytime an effect which requires it's service is ran.
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
