redux-toolkit
redux-toolkit copied to clipboard
add createAsyncThunk.forTypes
This might need some yak shaving with the name and I also want to maybe take another look at how .forTypes is called, because like this it gets more restrictive with every time it's called, but this should serve as a good prototype.
Please test and give comments.
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.
Latest deployment of this branch, based on commit daf9920ad9033565426c02fe1e99892bb80acf99:
| Sandbox | Source |
|---|---|
| Vanilla | Configuration |
| Vanilla Typescript | Configuration |
| rsk-github-issues-example | Configuration |
| @examples-query-react/basic | Configuration |
| @examples-query-react/advanced | Configuration |
| @examples-action-listener/counter | Configuration |
Deploy Preview for redux-starter-kit-docs ready!
| Name | Link |
|---|---|
| Latest commit | b3e12cee399cbf96d8c817d3da6e24f7112b29d4 |
| Latest deploy log | https://app.netlify.com/sites/redux-starter-kit-docs/deploys/62fba253d7cdd8000a63e835 |
| Deploy Preview | https://deploy-preview-2604--redux-starter-kit-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 settings.
I'd call it .withTypes, myself. (Some parallel with thunk.withExtraArgument, for example.)
I think the types are now where I want them, wanna take another look? :)