Question about Optional Services and Managed Runtime in Effect Typescript Library
I have a doubt about optional services. If I require a service in the top of another service, I mean at creation time as an optional service, and then include this last service, the one with the requirement, into managed Runtime, will this fail at managed Runtime creation or just at execution time? I'm asking because I have a bunch of services that I want to move into manage runtime, but I need to remove an Http request dependency they had and I thought that maybe making that service-header an optional service that will be available at request time will be enough.
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
