-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Remove defaultProps in DatePickeriOS #31605
Labels
Good first issue
Interested in collaborating? Take a stab at fixing one of these issues.
JavaScript
Resolution: Locked
This issue was locked by the bot.
Comments
lunaleaps
added
Good first issue
Interested in collaborating? Take a stab at fixing one of these issues.
JavaScript
Component: DatePickerIOS
labels
May 26, 2021
6 tasks
Hi @lunaleaps!, I want to take this issue |
@lunaleaps Can I take this issue? Edit |
@Fannolo Sounds good with me! Please request review from me when ready! |
facebook-github-bot
pushed a commit
that referenced
this issue
Aug 25, 2021
Summary: Closes issue #31605. This is part of a bigger issue that plans to remove defaultProps from class components in order to provide a smoother transition to functional components. ## Changelog [General] [Changed] - Remove defaultProps from the DatePickerIOS Component. [General] [Test] - Added snapshot test for the new component Pull Request resolved: #32064 Test Plan: Compiled the rn-tester folder to check if the behavior is consistent with the previous versions. Reviewed By: lunaleaps Differential Revision: D30492515 Pulled By: yungsters fbshipit-source-id: ed2c5f3211742d528ff3f8e406a53cd7ea43d7e7
@lunaleaps can we close this issue? Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Good first issue
Interested in collaborating? Take a stab at fixing one of these issues.
JavaScript
Resolution: Locked
This issue was locked by the bot.
See parent issue #31601
Expected Results
defaultProps
are removed in DatePickeriOSThe text was updated successfully, but these errors were encountered: