-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2023-10-23][$250] Upgrade lottie-react-native to 6.3.1 #28132
Comments
@roryabraham the |
Job added to Upwork: https://www.upwork.com/jobs/~012d74e563bdfd8754 |
Triggered auto assignment to @Christinadobrzyn ( |
Triggered auto assignment to @dylanexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Upwork job price has been updated to $250 |
Dibs |
ProposalPlease re-state the problem that we are trying to solve in this issueUpgrade lottie-react-native to 6.3.1 What is the root cause of that problem?There are breaking changes in lottie-react-native 6.0 What changes do you think we should make in order to solve the problem?We need to update version in package.json Also, we need to check updates for react-native-web-lottie What alternative solutions did you explore? (Optional)NA |
ProposalPlease re-state the problem that we are trying to solve in this issue.Upgrade lottie-react-native to 6.3.1 What is the root cause of that problem?NA RC What changes do you think we should make in order to solve the problem?
Since we can not support webpack/babel alias support for this package we can create a cross-platform component Just as a layer for the platform specific packages. Like inside components folder we would create
What alternative solutions did you explore? (Optional)NA |
I think we have a draft PR ready with |
Definitely out-of-scope for this issue. We're working building web support directly into lottie-react-native in #26871 |
📣 @mananjadhav Please request via NewDot manual requests for the Reviewer role ($250) |
@dylanexpensify It seems like @situchan has already reviewed the PR for this. |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-20. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-20. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Un-assigning myself since this was handled solely by @situchan! |
@roryabraham, @Christinadobrzyn, @dylanexpensify, @ZhenjaHorbach, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@Christinadobrzyn @dylanexpensify this is ready for payment |
Gotcha! Payment summary: Bug reporter: NA Bonus: N - based on #28132 (comment) Upwork job - https://www.upwork.com/jobs/~012d74e563bdfd8754 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Slack convo: https://expensify.slack.com/archives/C04878MDF34/p1695304606676759
Problem
There are breaking changes in lottie-react-native 6.0 and we're still using 5.1.6. There are E/App changes needed to complete #26871
Solution
Upgrade E/App to use lottie-react-native 6.3.1+
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: