Dmitry

Looks like you need to use `restore` and `attach` with function and without mapParams: ```js const helloFx = createEffect(async () => { return new Promise(resolve => setTimeout(() => resolve('hello'), 3000))...

Yes, it is, but this is a valid type, so there should be no void return. Is webstorm’s fork of typescript handle this case at all? Would you like to...

@maximelebreton [real application](https://github.com/ilajosmanov/braces-effector) with vue and effector

If we dig `maxHistorySize` a bit more then we find that this is an implicitly defined state, a state with requirement of having no initial state (thats why `restore` wouldn't...

By the way, the idea behind init modules is also to explicitly control the order in which side effects are being called during application initialization. So if you think you've...

Tl;tr: this idea looks reasonable and promising but how will you deal with events triggered before links in the module will be established? If you say you won't trigger events...

Another edge case: you can't port such an application to fork api because we can't keep global event history in any way

This is a data race in effect implementation: it works via _two_ sequential lowest priority calls, so sample seeps between them Minimal reproduction: ```ts const triggerEvent = createEvent() const triggerEffect...

Our plugin has options to disable particular transformations, in your case it will looks like that ```json { "plugins": [ ["effector/babel-plugin", { "domainMethods": { "domain": ["createDomain"] } }] ] }...

full set of options of that group: - storeCreators - eventCreators - effectCreators - domainCreators - restoreCreators - combineCreators - sampleCreators - forwardCreators - guardCreators - attachCreators - splitCreators -...