You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain APIs are going to need to change, although not very much, for v4. We should make a list of them.
call() This is very overused for noting scope, and also for evaluating promise. We are going to deprecate the bare promise
add notes on the what is changing about call(), and how to upgrade
add scoped() to V3. It will be just an alias to call(). One option for upgrade. Upgrade would involve replace call() -> scope() then fix TS errors.
Scope#run -> run(op, { scope })
ideally replace Scope#run -> Scope#spawn
action(): Action will become more like the promise constructor and will not take an operation function, but instead will take a simple function that receives a resolver to be called when the effect resolves. It is more a general effect resolver than anything else.
The text was updated successfully, but these errors were encountered:
Certain APIs are going to need to change, although not very much, for v4. We should make a list of them.
call()
This is very overused for noting scope, and also for evaluating promise. We are going to deprecate the bare promisecall()
, and how to upgradescoped()
to V3. It will be just an alias tocall()
. One option for upgrade. Upgrade would involve replace call() -> scope() then fix TS errors.Scope#run
->run(op, { scope })
Scope#run
->Scope#spawn
action()
: Action will become more like the promise constructor and will not take an operation function, but instead will take a simple function that receives a resolver to be called when the effect resolves. It is more a general effect resolver than anything else.The text was updated successfully, but these errors were encountered: