Conversation

Notices

1. Embed this notice
   Peter Toft Jølving (joelving@mastodon.joelving.dk)'s status on Sunday, 21-Jul-2024 16:57:30 JST Peter Toft Jølving

   in reply to

   • Daniel Supernault

   @dansup aaaand, now I see that you've already built it. Sorry!

   • Embed this notice
     Peter Toft Jølving (joelving@mastodon.joelving.dk)'s status on Sunday, 21-Jul-2024 16:57:31 JST Peter Toft Jølving

     in reply to

     • Daniel Supernault

     @dansup that would also let you keep the stores hydrated for those users that aren't currently active.

     And again, I may well be mansplaining like crazy here, and you probably know all this by heart. In that case, sorry!

   • Embed this notice
     Peter Toft Jølving (joelving@mastodon.joelving.dk)'s status on Sunday, 21-Jul-2024 16:57:32 JST Peter Toft Jølving

     • Daniel Supernault

     @dansup yeah, multi-tenancy can be a pain to retrofit. If you know ahead of time, that you want it, you can scope the data stores to individual users.
     One way to deal with it (if you want suggestions, otherwise sorry!) is to use a global singleton for storing active user ID and a factory that returns indivual data stores for each user ID and use that when injecting the data stores and changing the active account. Would that be feasible in your situation?