Dmitry

Yes, looks like `createApi` types are complex enough to cause issues with generic types. Generic types are common source of issues in typings, so I suggest to use createEvent explicitly...

Its ok to improve this case as we eventually have to deal with that anyway. Open questions are only implementation details: - The library is bundled as single file and...

Yes, it’s a good idea, we’ll go in that direction, maybe we could deprecate them altogether. Next major version should be relatively small, without large depreciations, so it’s planned for...

Good idea 👍

Note: farfetched uses this feature, need to provide an alternative or suggest a solution for this library in any way (slight refactoring for example)

You can write wrapper effect which will be resolved immediately and call it in beforeEach ```js const getUserRoutesWhenNeededFx = attach({ source: $userRoutes, async effect(routes) { if (!routes) { await getUserRoutesFx()...

`error.cause` is almost always are non-serialable, so we probably could just add default serialization to `$error` store: ```ts $error = createStore(null, { serialize: { read: error => error, write: ({cause,...

https://effector.dev/en/typescript/typing-effector/

Maybe we need to explicitly throw error instead of calling effect in any way

Yes, sure