react-native-paper
react-native-paper copied to clipboard
fix: remove deprecated use of defaultProps
Motivation
This PR prevents the error log warning the "defaultProps" will be removed (visible in RN0.74.0)
Related issue
Addresses #4382
Test plan
Ensure that use of the TextInputIcon does not produce the error (included in linked issue) when run using RN0.74.0
Hey @timbocole, thank you for your pull request 🤗. The documentation from this branch can be viewed here.
LGTM, This will be on version 5.12.4
Hi @gedu @sethimcclaine any Idea when is 5.12.4 scheduled for?
Hi all!! Thanks for the work!. So I shall wait until the next release ? and ignore the error message? Thanks!!!!!
Hi @gedu @sethimcclaine any Idea when is 5.12.4 scheduled for?
Hey, we are trying to upgrade paper to support almost latest RN version, and after that we will submit it, I hope as soon as possible
on RN 0.74.2 I get a warning with this problem.
Is there any update with this PR?
When it will be released to main?
The main maintainer of the library has been really busy these past days. I would like him to perform a final check on all the open PRs that will be merged for Milestone 5.12.4. Hope it will be soon
merge pleeease
merge please :pray:
Following the tradition of asking for a merge, could you please merge that one? 😆
How do I follow this pull request to know when it gets merged?
Why don't merge this PR? Many of people is waiting to be approved.
Merge the change finally. This isn't a breaking change or something, there are no reasons to keep this for months.
Merge the change finally. This isn't a breaking change or something, there are no reasons to keep this for months.
No way. The code broke. Is this because of that change?
This broke the update - https://github.com/callstack/react-native-paper/pull/4422/files
Also, there is a PR that will fix it - https://github.com/callstack/react-native-paper/pull/4466
Mostly will be available in the next release
I was about to say, not sure how this PR could be at fault! 😂 - Thanks @raajnadar for the update/fix.
This issue also affects version 4. What would be the best way to take this fix to that version as well?