-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
code mod for breaking syntax changes #2983
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
Comments
@balazsmatepetro I've added some examples for |
Thank you so much, it helps a lot! :) |
@balazsmatepetro how are things on the code mod? Do you need any help? |
Hi! I'm planning to open a PR at the end of this week. :) |
Task listWrite codemods for:
Additional tasks:
Things to address after our last sync with @TkDodo:
|
🎉 This issue has been resolved in version 4.0.0-alpha.13 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 4.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
useQuery, useInfiniteQuery, queryClient.fetchQuery, queryClient.prefetchQuery, queryClient.fetchInfiniteQuery, queryClient.prefetchInfiniteQuery, useInfiniteQuery
queryClient.invalidateQueries, queryClient.refetchQueries, queryClient.resetQueries, queryClient.removeQueries, queryClient.cancelQueries
queryClient.getQueryData, queryClient.getQueryState, queryCache.find, queryClient.getQueriesData, queryClient.isFetching, useIsFetching, useIsMutating, queryCache.findAll, queryClient.setQueriesData
queryClient.setQueryData, queryClient.setMutationDefaults, queryClient.getMutationDefaults, queryClient.setQueryDefaults, queryClient.getQueryDefaults
useMutation
same as
useQuery
, except thatqueryKey
ismutationKey
useQueries
An easy one because useQueries only gets an array passed, which should become an object. Nothing within query1 / query2 / query3 needs to change.
after that, inside the
queries
object, we need to changequeryKey
to be an array, like foruseQuery
with the object syntax.The text was updated successfully, but these errors were encountered: