Skip to content
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

Fix TypeScript tests to pass for new TypeScript definitions #2671

Closed
wants to merge 10 commits into from

Conversation

evgenyt1
Copy link

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?

timdorr and others added 10 commits April 25, 2017 12:18
…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
@timdorr
Copy link
Member

timdorr commented Oct 22, 2017

next is for proposed 4.0 stuff. It involves a major upgrade of TS, hence it's grouped into that release. No idea when it will land, though.

@timdorr
Copy link
Member

timdorr commented Oct 22, 2017

I just updated the next branch against master. Can you redo this? We're not using yarn now that npm has lockfiles.

@timdorr
Copy link
Member

timdorr commented Oct 22, 2017

BTW, looks like just b9278d1 is all we need in this PR.

@evgenyt1
Copy link
Author

Just confused.
Do I understand correctly, that PR #2674 is merged now and this one mine will be closed?

@timdorr
Copy link
Member

timdorr commented Oct 23, 2017

Yes, sorry, I meant to close this out too. Thanks for the effort!

@timdorr timdorr closed this Oct 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants