Add docs about batch() API to Performance FAQ
#3431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for redux-docs ready! Built with commit ed20766 |
|
Thanks! I'll tweak the wording a bit, and then merge this in. |
|
For sure :) thanks for all your hard work <3 |
webMasterMrBin
pushed a commit
to webMasterMrBin/redux
that referenced
this pull request
Aug 21, 2021
webMasterMrBin
pushed a commit
to webMasterMrBin/redux
that referenced
this pull request
Aug 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed in the v7 release we added support for the
batch()API. I know there are docs planned for upcoming releases but thought it could be something to mention in the Performance FAQ. In the section where we talk about batching updates, we still recommend in the FAQ other packages i.e.redux-batched-actions, etc.I feel it would be good to give users a heads up in this section to take a look if upgrading and using the new
batch()API would address their needs. I still left text relevant to users who have not upgraded yet though.If you feel this is unnecessary or if I can improve the docs in any way, feel free to reject or let me know :) We started using the
batch()API and it's been great.