Handling Dependencies in Large Effect Services
https://www.effect.solutions/services-and-layers Here kit recommends
What does this look like in practice? On some of the office hours streams they'll mostly show small examples where if Service B depends on Service A, Service B will grab Service A up top in its layer building effect and are then it's available to the method's via closure. What if your service has a large surface area and you want to define each method in its own file? Seems like the only option is to define the service method as a fn that takes in its service deps. To me that feels somewhat non effect-y. I understand the benfits of not leaking requirements unnecessarily but wondering if there are any patterns out there for large services. For example I'm writing a Slack bot so there's a SlackClient service that handles instantiating the sdk client and then there's a Slack service that exposes most of that slack client's methods after making them effectful, cleaning up some errors, and some other standardization processing. In that situation the recommendation would be to define all the Slack service methods by passing in the client right?
Service methods should have no dependencies (R = never). Dependencies are handled via Layer composition, not through method signaturesSomething similar is also mentioned in the main effect docs: https://effect.website/docs/requirements-management/layers/#avoiding-requirement-leakage
What does this look like in practice? On some of the office hours streams they'll mostly show small examples where if Service B depends on Service A, Service B will grab Service A up top in its layer building effect and are then it's available to the method's via closure. What if your service has a large surface area and you want to define each method in its own file? Seems like the only option is to define the service method as a fn that takes in its service deps. To me that feels somewhat non effect-y. I understand the benfits of not leaking requirements unnecessarily but wondering if there are any patterns out there for large services. For example I'm writing a Slack bot so there's a SlackClient service that handles instantiating the sdk client and then there's a Slack service that exposes most of that slack client's methods after making them effectful, cleaning up some errors, and some other standardization processing. In that situation the recommendation would be to define all the Slack service methods by passing in the client right?
Similar Threads
Was this page helpful?
