Testing Challenges with `Effect.Service` and Dependency Injection
I noticed that
Does this imply I have to stop passing dependencies and wire them up manually for my runtime in order to be able to test them?
Effect.Service makes it arguably difficult to write tests for business logic in the application layer, specifically when I add Repository.Default to the dependencies of my service. I can easily provide Service.Default to the test program, but it automatically uses the default implementation of the repository due my explicit entry in the dependencies array: https://effect.website/play#da29dce1e38aDoes this imply I have to stop passing dependencies and wire them up manually for my runtime in order to be able to test them?
