Fix StrictMode warnings
See original GitHub issueDescription
When wrapping the app with <StrictMode>
, there are warnings coming from internal react native components. They need to be updated to stop using the legacy context api and unsafe methods like UNSAFE_componentWillReceiveProps.
Also, I believe this is a prerequisite for Concurrent Mode support.
<div> </div>Environment
Environment
React Native Environment Info: System: OS: macOS 10.14 CPU: x64 Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 33.30 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 8.11.4 - /usr/local/bin/node Yarn: 1.10.1 - ~/.yarn/bin/yarn npm: 6.4.1 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1 Android SDK: Build Tools: 23.0.1, 23.0.3, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.0, 28.0.2, 28.0.3 API Levels: 19, 22, 23, 24, 25, 26, 27, 28 IDEs: Android Studio: 3.2 AI-181.5540.7.32.5014246 Xcode: 10.1/10B61 - /usr/bin/xcodebuild npmGlobalPackages: react-native-cli: 2.0.1
Issue Analytics
- State:
- Created 5 years ago
- Reactions:16
- Comments:7 (4 by maintainers)
Top GitHub Comments
Opened two PRs for ScrollView and AnimatedComponents/Touchables:
Will be working on this over the weekend.