Fixing issue #128: Default Props Error #1
Merged
Conversation
This file contains 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
…ers for functional components This PR addresses the deprecation warning related to the use of defaultProps in functional components, as seen in the warning message pointed in issue# 128: Warning: y: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR addresses the issue reported in jcmcneal#128, where a warning is displayed for using
defaultPropsin function components. The warning indicates that support fordefaultPropswill be removed in future major React releases.Issue was this
Changes:
Notes:
This refactor ensures compatibility with upcoming React updates while addressing the reported issue.