Question about Managing Dynamic Dependencies in Layers
This is part of the docs on layers. Is it generally a bad idea to avoid requirement leakage?
Say I have a dynamic dependency that needs to be provided not when the layer is created (in which this can be moved to the service implementation) but rather when yielding the effect and getting a value to be provided at runtime.
Say I have a dynamic dependency that needs to be provided not when the layer is created (in which this can be moved to the service implementation) but rather when yielding the effect and getting a value to be provided at runtime.
