-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Fix TypeScript tests to pass for new TypeScript definitions #2671
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
Conversation
…reduxjs#1569) * throw error if getState, subscribe, or unsubscribe called while dispatching * prevent throwing if not subscribed * update getState error message * fix space after period * update subscribe/unsubscribe error messages
* Add a doc section on dispatching during middleware setup. * Warn when dispatching during middleware setup. * Upgrade the warning to an error. * Update docs to match thrown error behavior.
* Add mapped type for combineReducers in index.d.ts Updated typescript to 2.1.4 Updated typescript-definition-tester to 0.0.5 Updated typescript tests to use proper import Added mapped type to index.d.ts * add strict null check for reducer Updated Reducer<S> type in index.d.ts Add strictNullChecks flag to typescript spec
Behavior has been replaced with the "it warns when dispatching during middleware setup" test in the 'next' branch.
* Revamp TypeScript typing with more type safety * Provide a default action type for combineReducers * Change state default types to any * Don't parameterize Dispatch with a state type * Remove docstring about excised type parameter
|
761b399
to
ee1b0aa
Compare
I just updated the next branch against master. Can you redo this? We're not using yarn now that npm has lockfiles. |
BTW, looks like just b9278d1 is all we need in this PR. |
Just confused. |
Yes, sorry, I meant to close this out too. Thanks for the effort! |
Fixed typescript tests for new d.ts
Use prepare instead of prepublish in package.json (same as in master branch).
Update typescript in yarn.lock to comply to what's in package.json
I'm using the
next
branch to have new d.ts and strongly typed actions.However wondering if the
next
branch is going to be synced with the current master?