Dmitry

Note that flow now has `opaque types`, which can help to declare type relations https://medium.com/flow-type/hiding-implementation-details-with-flows-new-opaque-type-aliases-feature-40e188c2a3f9 $Values and $ElementType can help too Also, if you use comment syntax, you can avoid...

Works when sample is placed near effect declaration https://share.effector.dev/5zxVkoYg Edge case, bug

We could check the scope by babel api to be sure that we works with correct import

There was a use case in effector 21 which depends on that buggy behavior: ```ts import {createDomain} from 'effector' export const {createStore} = createDomain() export const $foo = createStore(0) ```...

At the moment of any `fork` call, application graph should be already initialized, that's mean that plain `fn: () => App()` will be fired too late, so you need to...

I suggest to throw an error, as this is definitely a mistake

This will lead to strong inconsistency, because when effect defined as connected to store starts to do whatever it want, this won’t be a _test_ of behavior, but rather a...

Thanks for reproducing the issue, use cases with nesting and derived stores are a longtime headache for me

How will you determine _when_ to execute your function? I can only see one reliable approach: execute them during the first fork call, which implies that it should be used....

Well, in that case, what happens during an explicit unit call? The situation is divided into two: 1) Pending functions will not be called. The unit will be launched in...