-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$3500] Upgrade to react-native-web v0.19.6 or greater #16660
Comments
I synced our fork with the upstream yesterday, so our fork officially contains the 0.19 code. It's not published yet though. Assigning to myself to publish our react-native-web fork when this comes off HOLD. |
This is a big move but a good one. A lot of refactoring might be needed as many things have been changed https://github.com/necolas/react-native-web/releases/tag/0.19.0. Happy to help if needed. |
We had a couple of VirtualizedList fixes from #12054 included in 19.2 🎉 |
Still on HOLD |
Still on HOLD |
FYI: I added one more issue in the Problem statement, in the list of the issues held on this one. |
No update here, still on HOLD for the Accessible Pressables project, which is making steady progress. Technically we don't need to complete the project, we just need to get to a point where there's no more |
I opened a PR to sync again, this will unblock #19345 as one of the new release fixes an issue with batchSize > 1 and inverted FlatList. @roryabraham What is the reason for the hold on the pressables project? |
I believe RNW 0.19 removed all the |
I just verified and they got deprecated and not removed so it could still be usable before the Touchable migration project is done. We could add the warning to logbox ignore list until the migration is over. |
At this point, there are only 5 remaining |
Hey, I'm Arthur from Callstack and I'll start working on this 🙋 |
@arthurmfgtab there is a PR #24482 already, we just need some help here #24482 (comment) |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
What's the state of this? |
@iwiznia PR is already deployed to prod, it is awaiting a payment |
Oh nice! Can I unhold #10731 then? |
@iwiznia Yeah, we are now using |
@kevinksullivan this is ready for payment too. |
Upwork job price has been updated to $3500 |
Updating the bounty to $3500 as this was a larger issue with many sub-issues and conflicts |
Payments made |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Problem
There are a number of initiatives and bug fixes that depend on React Native 0.19. We can aggregate those all here:
Solution
Upgrade E/App to use react-native-web 0.19.
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @kevinksullivanThe text was updated successfully, but these errors were encountered: