-
Notifications
You must be signed in to change notification settings - Fork 867
Update typescript definitions, remove old definitions fix tests #312
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
package.json
Outdated
"pre-commit": "^1.1.3", | ||
"react": ">=0.13", | ||
"react-addons-test-utils": ">=0.13", | ||
"react": ">=15 <16", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you think these versions should be bumped?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically previous version still matches that but since react versioning has been change I just updated it. I can reverse that but still it would be good to add upper limit <16
in case there are changes that would break the library.
package.json
Outdated
@@ -76,6 +73,8 @@ | |||
"webpack-stream": "^3.2.0" | |||
}, | |||
"dependencies": { | |||
"@types/react": ">=15 <16", | |||
"moment": "2.16.x", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're aware moment
is not a dependency of this project, and we would like it to stay that way :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually it is dependency as it is used all over the place. When you use only version compiled by webpack/gulp/grunt/whatever then you don't really need anything as output will be just single file. However if you add this to your project dependencies in node-like environment you need to be sure the library is there and it's resolvable. So the moment
should be at least in peerDependencies
if not dependencies
.
I just noticed that it has been changed and react
along with moment
have been mover to peerDependencies
where they should be. I'll merge with master
and this should be good to go.
Hi @LKay and thanks for your contribution! Your changes seem to be removing the TS typings for version 1.8. I am not using TS and therefore I don't know much about what's going on in that world, but why do you want to remove support for 1.8? Has everyone started using TS 2.0+? |
It's not like nobody is using 1.8 but they are mostly legacy projects that haven't moved to 2.0+ yet. Since biggest repository for definitions, Definitely Typed moved to supporting only TS2.0+ natively for resolving typing and publishing them most of people already migrated. I could bring back the file but I'm sure it will be rarely used anyway. |
package.json
Outdated
@@ -39,11 +38,10 @@ | |||
"license": "MIT", | |||
"peerDependencies": { | |||
"moment": ">=2.16.0", | |||
"react": ">=0.13", | |||
"react-dom": ">=0.13" | |||
"react": ">=0.13 <16", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you think we should cap the version support?
package.json
Outdated
"react-addons-test-utils": ">=0.13", | ||
"react-dom": ">=0.13", | ||
"react": ">=0.13 <16", | ||
"react-addons-test-utils": ">=15", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you bumping this version?
There's a lot of things going on in this PR, and some changes are not motivated. I like that you want to upgrade to the recommended standard of TS 2.0+, but I don't see why we need to mess with the dependencies. |
@simeg I brought back the versions without caps to |
@LKay Thanks for updating, and thanks for making us stick to the standards. Out of curiosity - where can I find the documentation for the recommended TS 2.0 structure? Is it coming from Microsoft or DefinitelyTyped? Also, you have to rebase for this to get merged. |
@LKay Great, thanks. Oops I had the wrong option selected here on GitHub. Merging now. |
@simeg Is there anything pending yet for this being released as |
…feature-render-input * 'master' of github.com:YouCanBookMe/react-datetime: Version 2.8.11 Remove React.DOM references Remove maintainer wanted ad from README Add maintainer wanted ad to README Remove npm download counter from README Use correct @types-react version Remove moment as dependency (clean up after PR) Update typescript definitions (arqex#312) Bump version to 2.8.10 Increase click area of arrows for changing day/month/year Update the dist files with new modules Update examples to create-react-class Use PropTypes from module instead of React Use create-react-class, drop React.createClass Fix broken reference to LICENSE in README Bump version to 2.8.9 Reference correct file in build task fixed test that was used to document existing bug check date.month() for current active month
@LKay Why were the |
Description
Motivation and Context
Checklist