Skip to content
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

Roadmap v2 #556

Closed
30 of 34 tasks
stijnvanhulle opened this issue Oct 25, 2023 · 7 comments
Closed
30 of 34 tasks

Roadmap v2 #556

stijnvanhulle opened this issue Oct 25, 2023 · 7 comments
Assignees
Labels
alpha enhancement New feature or request
Milestone

Comments

@stijnvanhulle
Copy link
Collaborator

stijnvanhulle commented Oct 25, 2023

Why

Summary

Discord

Hi all, I created a roadmap on Github for v2: #556.
Why?

I have been working on some changes related to the architecture of Kubb which will make it faster and easier but it's taking more time to get it ready. So v2 will not be a breaking change but with the changes that will be added it can cause weird behaviours(don't want to do this with a major bump).

v2 will also include a rewrite of how react-query is getting generated so that all issues related to using useQuery and useMutation will be resolved(v4 and v5).

All of this will be added to the alpha tag on NPM and with the playground you can also select the alpha build: https://www.kubb.dev/playground.

Features/fixes

type PluginKey = [pluginName: string, identifier: number]

Explore

  • 📔 = docs added
@stijnvanhulle stijnvanhulle added bug Something isn't working enhancement New feature or request alpha and removed bug Something isn't working labels Oct 25, 2023
@stijnvanhulle stijnvanhulle added this to the 2.0.0 milestone Oct 25, 2023
@stijnvanhulle stijnvanhulle linked a pull request Oct 25, 2023 that will close this issue
@stijnvanhulle stijnvanhulle pinned this issue Oct 25, 2023
@stijnvanhulle stijnvanhulle self-assigned this Oct 25, 2023
@stijnvanhulle
Copy link
Collaborator Author

@la55u I added your issue for the mutation to the list(#530 (comment)). I will have a look later this week to fix it :)

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs
Copy link
Contributor

How about if deleting the deprecated client option is also added in v2?

@la55u
Copy link
Contributor

la55u commented Nov 1, 2023

React-query is further complicating things.. In v5 there is a separate hook now for queries if you want to make use of Suspense: useSuspenseQuery. AFAIK useQuery and useSuspenseQuery are for different use-cases: you have to use the first one if you explicitly don't want to use Suspense and the second one if you do, there is no option anymore to disable it on a per-query basis. Since most IRL projects will have edge cases where it's desired to be able to disable suspense behavior I suppose both useQuery and useSuspenseQuery custom hooks should be generated with kubb? Please someone correct me if I'm wrong I'm just getting started with react-query v5.

@kalagin
Copy link

kalagin commented Nov 5, 2023

Is RTK Query implementation planned?

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs
Copy link
Contributor

When do you expect the v2 release?

@stijnvanhulle
Copy link
Collaborator Author

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs Probably in a couple of weeks, it will depend on how much time I will have in the coming weeks :)

@stijnvanhulle
Copy link
Collaborator Author

@kalagin I would suggest using https://redux-toolkit.js.org/rtk-query/usage/code-generation with that it's maintained by the creators of Redux.

@stijnvanhulle stijnvanhulle unpinned this issue Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alpha enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants