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
React Native 0.60 tasks #1172
Comments
|
Are the update snasphot tasks simply taking the appropriate folder from RN 0.57 and replacing the folder in this project? If not, do you have the steps required for that type of task? Also, should we work off of RN 0.57.4 tag? https://github.com/facebook/react-native/tree/v0.57.4 |
|
Updated the OP. RN 0.57.5. Snapshots are of files, not directories. You'll also need to handle updating any new import paths or dependencies |
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
|
I'll try to take a look at |
|
I accidentally wiped out a bunch of commits on the |
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
Mirror contents of React Native 0.57.5 Ref #1172
|
I'm also curious about this issue. Won't apps using < 0.59 start being rejected from app stores starting in August because of 64bit? After that point it will more or less be impossible to use an old version like 0.55. |
|
Latest RNW works fine with RN 0.59, just officially not supported. |
What does it needs to get to be officially supported (besides an update in |
|
Hello, |
|
Hello, |
Adds the accessibilityState and accessibilityRelationship object props that map to ARIA props. Removes the accessibilityStates array prop that is not compatible with web accessibility services. Ref #1172
Adds the accessibilityState and accessibilityRelationship object props that map to ARIA props. Removes the accessibilityStates array prop that is not compatible with web accessibility services. Ref #1172
|
I have RNW working with RN 0.60 after doing multiple config overrides using webpack and babel, but unable to get a production build. Waiting for official support so we can override the hacks.
|
|
@prade can you be able to publish your hacks in a pull-request? This way they could be easier merged in master. |
|
And not only that, that also they could be used by others. |
|
Hello |
Adds the accessibilityState and accessibilityRelationship object props that map to ARIA props. Removes the accessibilityStates array prop that is not compatible with web accessibility services. Ref #1172
|
Decided not to add more
|
|
Updating babel-plugin-tester is currently blocked on babel-utils/babel-plugin-tester#50. Edit: babel-plugin-tester's unit tests didn't catch the change, and the author closed the issue. I will stick with v5 and stop using babel-plugin-tester in the future. Alternatives: https://babeljs.io/docs/en/next/babel-helper-plugin-test-runner.html, https://github.com/satya164/babel-test |
|
Helo, I am just discovering react-native and I wonder if I should use it for the cross platforme native and web app I want to build. I see that 0.60 of react-native is out but this is blocked for a while and there's no milestone or release date for this. Can I have you people users opinions, should I expect to be able to upgrade to 0.60 without pain the future if I start building my app with react-native-web or should I just not use react-native-web ? Thanks for sharing ! |
|
@kopax |
|
I still do not have my answer and so far I have expo, and making my own. I have not decided yet. Not sure if this should be use, but shouldn't be too hard to make your own react-native-web I am also thinking this as a solution. |
|
I don't know what you're asking. Nothing is blocked on anything and Expo uses RNW with RN 0.60. I'm going to close comments on this issue because they're not helpful and most of the work is complete and will land in master in good time |
Tasks related to changes in React Native 0.60.
Add touchable support toText(Text: onLongPress support #1011) (@DaKaZ)ScrollViewViewTextTouchablesnapshot (@necolas)TouchableHighlightsnapshot (@necolas)TouchableOpacitysnapshot (@necolas)TouchableWithoutFeedbacksnapshot (TouchableHighlight crashes when children are wrapped in Fragment #1105) (@necolas)forwardedRefprop toTextforwardedRefprop toViewaccessibilityStateaccessibilityRelationshipaccessibilityStatesaccessibilityTraitsaccessibilityComponentTypecontext.isInAParentTextw/React.createContext(@awinograd)ListViewsnapshot (Requires types for ScrollView) (@necolas)PanRespondersnapshotSwipeableListViewsnapshotclassName(Notice: intent to deprecate and remove className prop from View and Text #1146) (@necolas)Animatedsnapshot (@necolas)Batchinatorsnapshot (@necolas)FillRateHelpersnapshotFlatListsnapshot (@necolas)NativeEventEmittersnapshotSectionListsnapshot (@necolas)SwipeableFlatListsnapshot (@necolas)ViewabilityHelpersnapshotVirtualizeUtilssnapshotVirtualizedListsnapshot (@necolas)VirtualizedSectionListsnapshot (@necolas)Afterwards:
accessibilitySetSizeaccessibilityPosInSetdirection(incnone)accessiblefocusableThe text was updated successfully, but these errors were encountered: