V4 will contain almost 0 breaking changes for most people. Upgrading should be straight forward. I want to use v4 as a stepping stone, a chance to bring the library into the modern era so when we do have big changes to make, we can focus on those rather than tooling or build steps.
If you have another suggestions for v4 other than the goals I listed below, I would love to hear them. Whether that is new features, perf improvements, or anything else, I would love the feedback. I know the library has been a bit stagnant lately, and I am not sure how much time I can put in to adding new features, but I definitely want to hear all the feedback.
My goals for v4 are as follows.
Convert all 3 packages to TypescriptDone
Bring all packages used in repository to the latest version, including, but not limited to react (v16/17), redux, typescript, eslint, jest, etc In Progress
Fully leverage yarn workspaces (yarn v1)
Investigate and make decisions on our build pipeline, especially looking at the need to continue using webpack and babel, or just relying on typescript, and hopefully simplifying how that whole process works.
Simplifying/Automating the NPM deploy process.
Address all github security alerts
add a create-react-app template for redux-query. Allowing react users to run yarn create-react-app my-app --template redux-query and get the backbone of redux query setup for you with react
Move base branch to main instead of master
Stretch goals/feedback required
1) Deprecate connectRequest. Keep in redux-query-react, but throw a deprecation warning if used and update docs to say we will be removing this in the future.
2) Add dev performance apis that hook into popular performance tools (react profiler, logging tools, etc)
3) Add generic instrumentation support, could include performance instrumentation too
4) build template network interface, to allow people to easily build their own.
5) build Axios network interface
6) Better integration with GraphQL (this might be a version on its own)
Other misc goals:
Building out templates for PRs and Issues, making requirements for both more clear
Making sure all documentation uses inclusive phrasing, and updating where necessary.
Adding a better Contributors part of the site, to recognize community members who have put in time to this repo
This is the new branch for v4 of redux-query.
V4 will contain almost 0 breaking changes for most people. Upgrading should be straight forward. I want to use v4 as a stepping stone, a chance to bring the library into the modern era so when we do have big changes to make, we can focus on those rather than tooling or build steps.
If you have another suggestions for v4 other than the goals I listed below, I would love to hear them. Whether that is new features, perf improvements, or anything else, I would love the feedback. I know the library has been a bit stagnant lately, and I am not sure how much time I can put in to adding new features, but I definitely want to hear all the feedback.
My goals for v4 are as follows.
Convert all 3 packages to TypescriptDonecreate-react-apptemplate forredux-query. Allowing react users to runyarn create-react-app my-app --template redux-queryand get the backbone of redux query setup for you with reactmaininstead ofmasterStretch goals/feedback required 1) Deprecate
connectRequest. Keep inredux-query-react, but throw a deprecation warning if used and update docs to say we will be removing this in the future. 2) Add dev performance apis that hook into popular performance tools (react profiler, logging tools, etc) 3) Add generic instrumentation support, could include performance instrumentation too 4) build template network interface, to allow people to easily build their own. 5) build Axios network interface 6) Better integration with GraphQL (this might be a version on its own)Other misc goals:
Contributorspart of the site, to recognize community members who have put in time to this repomastertomain