-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
RTK 1.8 and 1.9 planning #2003
Comments
maybe a |
Unrelated but as a note for later: we should link the RTKQ "Essentials" tutorial pages from the RTKQ "Overview" page: https://www.reddit.com/r/webdev/comments/sc6eoc/redux_toolkit_query_is_no_one_using_it/ |
Another docs suggestion (possibly for me to implement): add more info/examples about dealing with errors. In particular, explaining the difference between a fetch error and serialized JavaScript error. https://stackoverflow.com/questions/70899492/redux-toolkit-do-not-send-request-when-query-param-is-invalid/71002555?noredirect=1#comment125554343_71002555 |
@lindapaiste that would be a very welcome contribution! |
Throwing this here for lack of anywhere better: https://www.reddit.com/r/reactjs/comments/q6lit4/thoughts_about_redux_reactquery_together/i0s3f27/
|
We should also deprecate the object notation of I did some experiments - while removing is not a problem, deprecating the extraReducers object notation seems impossible. It would require adding a second overload to createSlice and that breaks half the inference (seems to be a TS quirk). So I would suggest deprecating it with a runtime warning in dev instead. |
If @FaberVitale can pull off the Suspense support in #2245 , that would presumably be 1.9 as well. |
We need to upgrade Line 43 in 0050738
Are there features in the codebase that need IIRC there was an issue with ApiProvider:
|
Hmm. That is going to make versioning interesting :) Given that the rest of RTKQ's features work with any version of React that has hooks... maybe we accept a React peer range of 16.8+, but have a runtime dev check in the suspense functionality that throws an error if it isn't a high enough React version? Also we may need to update all of our examples and tests to work under React 18 as well. And yeah, that line in |
I opened a PR for that ApiProvider bug. |
@markerikson @phryneas I've made an additive feature request in #2355 and if 1.8 and 1.9 are possibly going to be the last releases before 2.0 then I'd like to ping y'all to get some priority feedback on it. I don't know how big of an effort it would be, but if it's a feature that you'd support adding to RTK Query - I'm willing to take a stab at implementing it. |
I have opened a discussion #2361 (comment)
toggleFieldOfUser: builder.mutation<boolean, string>({
query: (id) => ({
url: `/users/${id}`,
method: "PUT",
}),
invalidatesTags: cacher.cacheByIdArg("User"), // <----------------------- this will remain !
skipAutomatedInvalidationForLastFocusedQuery: true; // <--------------- additional option (optional)
transformResponse: (result: { success: true }) => result.success,
async onQueryStarted(arg, { dispatch, queryFulfilled, getState }) {
// manual cache update implementation. <--- just for the last-focused query, we will deal with ourself
} |
The React 18 upgrade is live here: #2409 #2409 is partially for maintenance but it also required for #2245 |
Pasting notes from today's triage call:
Also, not 1.9 related, but:
|
Status notes from Lenz:
|
Afraid I didn't do anything on this for about a month - been playing lots of golf, and work's been busy. But, golf season is coming to an end, and I want to pick this up and push it through soon. I've got tomorrow free and Monday off, and I intend to focus on RTK 1.9 work. |
1.8:
configureStore
andgetDefaultMiddleware
Initial notional items for 1.9:
createSlice
What else would we want to get in?
Existing milestone: https://github.com/reduxjs/redux-toolkit/milestone/7
Looking through the issues, other candidates:
updateMany
on sorted entity adapter #1860upsertQueryData
functionality #1720For the record, I think this probably ought to be the last feature release before we look at doing RTK 2.0 and dropping IE11 compat ( ref: #958 )
The text was updated successfully, but these errors were encountered: