Best Practices for Managing Requirements in Effect.Service
So when it comes to managing requirements across your app, is it usually better to provide everything you can in the dependencies array inside your Effect.Service, just let everything bubble up and provide at the edge of your app, or some third way where you only let some bubble up?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
