Understanding use of Layers with incremental adoption
I've put together a fairly minimal example of an app with a couple layers of requirements, including some config loaded from env vars.
Trying to figure out how it might look to incrementally adopt Effect by wrapping an existing module in my application without making any changes to the original module. While still being idiomatic and light-weight for the new effect parts.
Is there a cleaner, more idomatic, or light-weight way to do this? Keeping in mind this is a simple representation of a larger slice of an app... so the aim isn't to eliminate all unnecessary layers. (code in thread)
Trying to figure out how it might look to incrementally adopt Effect by wrapping an existing module in my application without making any changes to the original module. While still being idiomatic and light-weight for the new effect parts.
Is there a cleaner, more idomatic, or light-weight way to do this? Keeping in mind this is a simple representation of a larger slice of an app... so the aim isn't to eliminate all unnecessary layers. (code in thread)
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
