EL AYADI Mohamed
EL AYADI Mohamed
Hello, I created the following issue on react-router's repo, but I know the issue is related to rollup. The build passes on a linux container (even inside windows). But fails...
The dependencies pattern is very useful and acts like a closure warrantee. But it would create unintentional bugs and also would need to add things that should not depend on...
## Creation path - Separate all creation paths of async state and display it in devtools: createSource, a hook, provider, intermediate (props.runp) ## Lanes - `lanes` should be attached to...
This list will contain all things that will be pushed as patches after the v1 lands: - [x] merge payload as member - [x] removal of source utilities that can...
The library needs to be tree shaked following these modules: - core async state - useAsyncState - useSource - useProducer - Provider - useSelector -
The read api should allow to specify whether to suspend on initial status, and also whether to throw on error status. ``` function read(suspendingStatuses, throwingStatuses) { if (suspendingStatuses[currentState.status]) throw suspender;...
After the v1, the v2 idea is: The following are breaking changes: - No provider at all - Key is the definition of the state and there will be a...
Now, when the producer starts working, it cannot be stopped and state is updated. We need a way to stop running before the first promise encounter. something like: props.bailout(reason); props.dontRun(reason);...