TypeError: Cannot use 'in' operator to search for '_op' in undefined about effect HOT 7 OPEN

Yes, i understand that i need to provide TestContext in order to use TestClock, i also understand that it is not tracked at type level, but the error in runtime doesn't provide a clear understanding of whats going wrong, is it intended?

from effect.

not sure we have enough info at runtime to make it nice

Something like "Some of the required dependencies not found" message would be better that TypeError at runtime anyway IMHO:)

And, BTW, maybe we could depend on Clock on type-level, and substitute it with TestClock when needed?

from effect.

To use TestClock you need to provide a TestContext like:

import {Effect, TestClock, TestContext, Schedule} from "effect"

const test = Effect.gen(function* () {
    const sleeps = yield* TestClock.sleeps();
    console.log(sleeps);

}).pipe(Effect.repeat(Schedule.addDelay(Schedule.forever, () => '1 second')))

Effect.runPromise(test.pipe(Effect.provide(TestContext.TestContext)))

The reason this is not tracked at the type level is because otherwise test implementations wouldn't be composable with app code so we opted for a fiber ref

from effect.

We can try to improve the error message but not sure we have enough info at runtime to make it nice

from effect.

We can try to improve the error message but not sure we have enough info at runtime to make it nice

Is there any way to make this code fail at compile time?
Without it, dependency injection works as a dynamic service locator and will cause heavy debugging.

from effect.

We can try to improve the error message but not sure we have enough info at runtime to make it nice

Is there any way to make this code fail at compile time? Without it, dependency injection works as a dynamic service locator and will cause heavy debugging.

As explained it is like this intentionally. For typed dependencies you have Context, in this case we use a FiberRef to not have explicit types. If using the TestClock added a dependency to the type you would not be able to use it in place of production code.

from effect.

from effect.