Sova
@Lonli-Lokli Is it still actual?
What about to assign a code to each error and add link to these pages in `throw` function? https://github.com/effector/effector/blob/master/src/effector/throw.ts#L1 Something like: ```ts export function assert(condition: unknown, message: string, code?: number):...
@uulaal Can you check this issue on the latest effector version?
@Komar0ff Hi! What do you think about continue work?
@ilajosmanov What do you think not to merge `useVModel` with `useUnit` at this stage of discussion? It should be very simple method at the first implementation, I think
Slightly improved readability: https://share.effector.dev/GfuRFJJ2
Effect has much documentation, and user content about current API. If we change it these hude work will be obsolete and we'll need to recreate them. I don't think we...
> People do not read documentation. This is not the reason to change the main API to a totally different. > No one uses sample and 'clock' in business rules....
Maybe get rid of javascript there? No one programming language can correctly describe natural language.
You can review [`patronum/spread`](https://github.com/effector/patronum/tree/main/spread) method for your case. ```ts const $first = createStore("") const $second = createStore("") const receiveMonolith = createEvent() spread({ source: receiveMonolith, targets: { first: $first, second: $second,...