Roadmap for 0.62
See original GitHub issueRN 0.62 recently cames out. I didn’t find any release issue nor a milestone that might fit so here are a list of things to handle. I might have forgotten some, I quickly review RN 0.62 changelog
-
ref
of an Animated component is now the internal component and deprecatedgetNode
- Add isReduceMotionEnabled() plus reduceMotionChanged to AccessibilityInfo https://github.com/facebook/react-native/commit/0090ab32c2aeffed76ff58931930fe40a45e6ebc
- new
Appearance
module (withgetColorScheme
) &useColorScheme
hook - missing props on Touchables (need to be detailed)
-
AccessibilityInfo.fetch
deprecated - Add getNativeScrollRef method to FlatList component
- ScrollView
scrollWithoutAnimationTo
removed - TextInput
onTextInput
removed - TextInput
inputView
removed - TextInput
selectionState
removed - TextInput ref change https://github.com/facebook/react-native/commit/bbc5c35a61cd3af47ccb2dc62430e4b6a4d4e08f
-
ref
on most primitives is now the host component with other methods attached (stop-gap until something likeReactNative.measure(hostRef)
lands) -
accessibilityValue
prop - Remove PropTypes
- Remove accessibilityStates
- Animated
useNativeDriver
is now required. - TimePickerAndroid removed
- Platform.select now supports native as an option
- Add HostComponent to the public API of React Native
BTW @necolas what do you think about having a version number that is more expressive about the version that is supported (= match 0.x, RNW 0.62 would means that it in sync with RN 0.62 API ) ?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:14 (12 by maintainers)
Top Results From Across the Web
0.62.0c Hotfix - Eternal Return
Disconnection pop-ups have been fixed to no longer appear in certain situations. Purchase buttons no longer appear for skins unavailable for purchase. Recent ......
Read more >dbRaevn on Twitter: " Australian COVID-19 vaccination roadmap As ...
Australian COVID-19 vaccination roadmap As of 20th September 2021 #COVID19Aus ... 0.74% since yesterday (14-day avg: 0.62%) 8.71% since 14 days ago.
Read more >Dealer's Life updated: version B:0.62 – Abyte Entertainment
We just released an update for Dealer's Life, bringing this new version (B:0.62) to all our players! Now, let's talk about the changes,...
Read more >V 0.62 || Custom Key Binding || PSX Mode :: No Time Events ...
V 0.62 || Custom Key Binding || PSX Mode. View full event information here: ... The first of a number of updates for...
Read more >SEO Funnels – How To Develop A Roadmap of Exceptional ...
How to develop an SEO Funnel of organic traffic that increases leads, sales, and profit. Follow this step-by-step process today. Learn more.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I understand that you can disagree with some choices (I disagree too), but I think it would be nice to stick to RN APIs to avoid to break RNW promise to mimic RN on the web (“React Native for Web”).
Even if we decide not to implement some stuff, we should at lease add “placeholder” so the code just don’t break on compilation, even if the behaviour is incorrect.
Missing props on Touchable => https://github.com/facebook/react-native/commit/8c0c860e38f57e18296f689e47dfb4a54088c260
onSlidingComplete => https://github.com/facebook/react-native/commit/c7aa6dc8270c0eabc913fe6c617c8131e3f4b3c5
Maybe one of you can submit a PR for it