Add support for new prop-types package #172
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
11 tasks
|
@fkling Could you please merge it and publish a new release? |
danez
approved these changes
Apr 12, 2017
|
Thank you! |
fkling
pushed a commit
that referenced
this pull request
Apr 13, 2017
|
Publish in v2.14.0 and v3.0.0-beta3. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves #171.
React 15.5.0 introduced a new
prop-typespackage and deprecatedReact.PropTypes. Currentlyreact-docgendoesn't recognize theprop-typespackage as a React module, so it sets thetypetocustomfor all PropTypes.