-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Fix rename legacy component lifecycles #22125
Fix rename legacy component lifecycles #22125
Conversation
Generated by 🚫 dangerJS |
UNSAFE_
prefix
Hi @yushimatenjin! Thanks for the help! Is this related to #22100? I plan to combine those entries in the changelog to a single entry, so the changelog section in this PR is n/a. I'll make sure that once this PR lands, you're attributed for your contribution. |
This pull request is not #22100 I'd like to do #22100 |
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.
@mmmulani has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
ありがとうございました!🙇🏾♂️ |
@yushimatenjin merged commit c293f29 into |
Summary: Adding an “UNSAFE_” prefix to `componentWillMount`. If this PR fixes an issue, type "Fixes #issueNumber" to automatically close the issue when the PR is merged. - [x] yarn test - [x] yarn flow - [x] yarn flow-check-ios - [x] yarn flow-check-android [General] [Fixed] - adding an UNSAFE_ prefix Pull Request resolved: facebook/react-native#22125 Differential Revision: D13237831 Pulled By: mmmulani fbshipit-source-id: b4ca1e4628f93e89fd5680c40b0e3f7c7db6ad38
Adding an “UNSAFE_” prefix to
componentWillMount
.If this PR fixes an issue, type "Fixes #issueNumber" to automatically close the issue when the PR is merged.
Test Plan:
Release Notes:
[General] [Fixed] - adding an UNSAFE_ prefix