Seeking Best Practices for Effect-Powered API in Electron App
Hey all, I’m looking for Electron app best practices.
Specifically, I need to have an Effect-powered API run on main and exposed to renderer via contextBridge. There are various services that need to be (a) shared across api functions, and (b) persisted for the lifetime of the session.
For (a), the answer to this is to merge all layers before providing them to each function, right? (Docs - Layer Memoization)
For (b), I found some answers from searching Discord involving Effect.never, but wasn’t sure how to apply that in this case with multiple api functions
Thanks for any tips
Specifically, I need to have an Effect-powered API run on main and exposed to renderer via contextBridge. There are various services that need to be (a) shared across api functions, and (b) persisted for the lifetime of the session.
For (a), the answer to this is to merge all layers before providing them to each function, right? (Docs - Layer Memoization)
For (b), I found some answers from searching Discord involving Effect.never, but wasn’t sure how to apply that in this case with multiple api functions
Thanks for any tips
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
