Understanding Service Provisioning in Effect Pipelines

I asked this question yesterday but the answer didn't seem to work (I probably just didn't quite get it). So as I get it now the services are always scoped to whatever Effect they are provided to. It's a little counter-intuitive because they are provided after the Effect like:

SomeKindOfEffect.pipe(Effect.provideService(MyService, MyServiceCreator()))

SomeKindOfEffect.pipe(Effect.provideService(MyService, MyServiceCreator()))

So in the above, the service is provided after the Effect. So in a case like the following, where is the service provided? Effect A, B, C, and/or D?

Effect.pipe(A.pipe(B, Effect.provideService(MyService, MyServiceCreator()), C), D)

Effect.pipe(A.pipe(B, Effect.provideService(MyService, MyServiceCreator()), C), D)

And this is just trying to wrap my head around for the real question, which is if there is a way I can provide context in a generator-like way for the whole rest of the generator without having to wrap it all and pipe it?

const myfunc = Effect.fn("myfunc")(
  function* (n: number, ...etc) {
    yield* Effect.provideService(MyService, MyServiceCreator(n)) // this doesn't work
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfunc = Effect.fn("myfunc")(
  function* (n: number, ...etc) {
    yield* Effect.provideService(MyService, MyServiceCreator(n)) // this doesn't work
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

Is there a way to provide the service , like the above, to A,B,C, and D? Without having to wrap the entire effect as you would in a pipe. Or, if you do have to wrap the function in an Effect.provideService(), what's the cleanest way to do it without having to pollute the codebase with extra effect functions just to provide services? E.g. the following looks quite ugly and unnecessarily verbose:

const myfuncAfterService = Effect.fn("myfuncAfterService")(
  function* (...etc) {
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfunc = (n : number, ...etc) => Effect.provideService(myfuncAfterService(...etc), MyService, MyServiceCreator(n))

const myfuncAfterService = Effect.fn("myfuncAfterService")(
  function* (...etc) {
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfunc = (n : number, ...etc) => Effect.provideService(myfuncAfterService(...etc), MyService, MyServiceCreator(n))

Understanding Service Provisioning in Effect Pipelines

SomeKindOfEffect.pipe(Effect.provideService(MyService, MyServiceCreator()))

SomeKindOfEffect.pipe(Effect.provideService(MyService, MyServiceCreator()))

So in the above, the service is provided after the Effect. So in a case like the following, where is the service provided? Effect A, B, C, and/or D?

Effect.pipe(A.pipe(B, Effect.provideService(MyService, MyServiceCreator()), C), D)

Effect.pipe(A.pipe(B, Effect.provideService(MyService, MyServiceCreator()), C), D)

const myfunc = Effect.fn("myfunc")(
  function* (n: number, ...etc) {
    yield* Effect.provideService(MyService, MyServiceCreator(n)) // this doesn't work
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfunc = Effect.fn("myfunc")(
  function* (n: number, ...etc) {
    yield* Effect.provideService(MyService, MyServiceCreator(n)) // this doesn't work
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfuncAfterService = Effect.fn("myfuncAfterService")(
  function* (...etc) {
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfunc = (n : number, ...etc) => Effect.provideService(myfuncAfterService(...etc), MyService, MyServiceCreator(n))

const myfuncAfterService = Effect.fn("myfuncAfterService")(
  function* (...etc) {
    yield* A(...)
    yield* B(...)
    yield* C(...)
    yield* D(...)
  })

const myfunc = (n : number, ...etc) => Effect.provideService(myfuncAfterService(...etc), MyService, MyServiceCreator(n))

Understanding Service Provisioning in Effect Pipelines

Similar Threads

Understanding Service Provisioning in Effect Pipelines

Similar Threads

Similar Threads

Similar Threads