-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update redux dependency to use built-in redux typings? #2
Comments
Hello, |
Wouldn't that be a step backwards? |
I don't think so. TS 2.0 will introduce own solution for management typings and they will be based from DT versions/DT registry |
Isn't that what typings is as well? |
Typings is different story. TS will use NPM resolving method, typings does that by inlining dependencies into resulting file (i don't like that). Although as i know typings will work with new TS typings management by placing local typings. |
Is there any info for that? All I can find is a line in their Roadmap:
|
microsoft/TypeScript#7156 third comment |
So the version of redux-form on DT doesn't use the redux definition that redux provides. It's still the old one. |
Yes, it linked to the old redux typings. But in TS 2.0 typings resolution (it will replace ///reference path to ///reference types also) the bundled definition from redux will have precedence over DT version even if |
I'm not too concerned with how the definition is pulled in. But I guess I'm just lost on how that makes a difference since the definitions are incompatible with each other. DT: interface Dispatch extends Function {
(action: any): any;
} Redux: export interface Dispatch<S> {
<A extends Action>(action: A): A;
} |
The redux package now includes built in types. This is causing some conflict errors (as there are some incompatibilities). Could this package be rewired to use those typings?
The text was updated successfully, but these errors were encountered: