-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Experiment with createDynamicMiddleware idea #3256
Conversation
Open in CodeSandbox Web Editor | VS Code | VS Code Insiders |
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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 3b60f85:
|
having a dist/react folder seems to cause interference with RTKQ's 'react' imports - as suggested by @markerikson I've tried this on the v2.0 integration branch and this no longer occurs. As such I think this MR will need to be rebuilt to aim at that branch, so a @reduxjs/toolkit/react entry point can be added cleanly. Technically the main part of this is not react specific, but I think a large reason to add this instead of just using existing solutions is for the ability to get a useDispatch hook that knows about injected middleware's type signature. |
closing in favour of #3292 |
see #3252 - opening PR to get a package to play with