New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v4 #555
Milestone
Comments
|
This issue contains a list on minor changes, which is not so relevent anymore, as we want to change a little bit more: #841 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We plan to release a new major version each year.
No heavy breaking changes, only improvements around some quirks of existed API.We found a way to hidectx
and make the code more natural. This is the most required feature and we glad to be able to implement it fast as possible. Many features of reatom/effects and reatom/async will be integrated to the core package for better performance and less complex realization, it will be allow you to usewithCache
for regular atoms and actions, which is unbelivable cool. But we will try to not change things a lot:atom
,action
,pipe
,onChange
,onCall
will the same, as many other APIs.Here is the list of notes what we should to change.
AtomCache
from the third argument ofonUpdate
callback. Passparams
to the third argument ofonUpdate
callback.spy
method fromCtx
(it should have no any effect for existed code)ctx.spy(({ params, payload }) => )
toctx.spy((params, payload) => )
ctx.spy
for atoms on initiatesubscribe
fromonConnect
to prevent connection stackcallSafely
isvoid
with*
(mutable) operator applies multiple timesmock
method?AsyncOptions
hooks to forceonUpdate
using for consistent codestyleabortControllerAtom
as a public property ofAsyncAction
coz in mostly internal thing, which behaviour could be not obvious for a userthrowIfAborted
instead of ponyfil from the utilswithReducers
should acceptctx
by the first argumentctx.get(callback)
API and and explicitbatch
API or allow to delay updates to a next tick for autobatchingnull
variant fromAtomCache['cause']
dataAtom.reset
should return the last (not new) state, to use it for a rollbackbind
from reatom/lens to ... something else.getRootCause
should acceptCtx
and the realisation should be justctx.get(read => read(__root)!)
ctx.controller
should be removed, the feature will be replaced with instence ofCauseContext
after
optional parameter fromretry
ofwithRetry
withRetry
should wrap returned promise which shouldn't fail during retryingThe text was updated successfully, but these errors were encountered: