Open EskiMojo14 opened 4 months ago
This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
Name | Link |
---|---|
Latest commit | 1d687e0a6d5b8119be2c55bcb7992a2679e8818b |
Latest deploy log | https://app.netlify.com/sites/redux-docs/deploys/6623d17363014500086c16b9 |
Deploy Preview | https://deploy-preview-4665--redux-docs.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
name: :book: New/Updated Documentation Content about: Adding a new docs page, or updating content in an existing docs page
PR Type
Updating existing page
Checklist
What docs page is being added or updated?
For Updating Existing Content
What updates should be made to the page?
Now that RTK has its own code-splitting utilities (combineSlices and createDynamicMiddleware), it would be very useful to have an in-depth of how these are intended to be used, separate from the API reference.
Do these updates change any of the assumptions or target audience? If so, how do they change?
This would avoid the standard "recipe" approach in the current docs in favour of depending on an actual library.