How can unuse always have a currentSub/Scope?

[Shinigami92]

@JounQin @teleskop150750 I just watched a video today about reactivity and that reminded me that with the reactivity system, there is a activeSub/activeScope which is by default undefined.
So this would mean, using an unSignal would not really receive any scope, because there is no outer "global" scope, is it?

I Vue, Angular, React and Solid, these are normally inside the "App" (as far as I know). But unuse does not have an App, cause it could/should also run e.g. inside node backend and without a global wrapper 🤔

Do we have an issue here?

[teleskop150750]

it doesn't have to be global/unEffectScope. using effect will create avtiveSub

[Shinigami92]

Got it! thanks for the hint.

I misread this line:

unuse/packages/unuse-reactivity/src/unEffect/index.ts

Line 31 in 401f6d4

const prev = setCurrentSub(state);

I thought the outer sub will be set and later the prev sub will be set back again. But it is not "the outer sub" but the "state" which then acts as sub 👍