-
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
[HOLD for payment 2023-04-03] Clean-up react-native-web workaround and fix it upstream #14278
Comments
Triggered auto assignment to @sophiepintoraetz ( |
@sophiepintoraetz sorry I think this does not need to be handled as bug, just to track this and have room for updates. |
Thanks @mountiny I'll try to recreate the bug extrenally and report it in react native web I'll submit a fix for Expensify's fork and the mainstream react native web repo |
Thanks! |
Making this Weekly as it might take a while to get the maintainer to approve the payment, this is mainly for tracking |
This issue has not been updated in over 15 days. @kidroca eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
@kidroca Could you link the upstream PR here please? |
Yeah, sorry I haven't published it yet I think I need to post 2 PRs
|
I see thanks for the context |
Sorry, I've been working on other issues - I'll the PRs about this today |
I've opened a bug report on the upstream repo |
Created a PR for the main repository |
I am gonna have to release out fork, instructions https://stackoverflowteams.com/c/expensify/questions/13855 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.89-0 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-04-03. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
@mollfpr I think you have reviewed and tested the PR, can you comment here so I can assign you |
@mountiny fyi you can manually assign C+ w/out them needing to comment 👍 |
Waaaaat, they were not showing up in my list, maybe I could scroll and I did not. Thanks! |
Weird!! Hope it works next time 😬 |
@mollfpr this still needs to be paid for your review and testing right? |
@mountiny Yes! |
Current assignee @dylanexpensify is eligible for the Bug assigner, not assigning anyone new. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@dylanexpensify could you please pay $1000 to @mollfpr for PR review and testing, thank you! |
On it! @mollfpr here's the job to apply to! https://www.upwork.com/jobs/~01340b9f282d5e934e |
@dylanexpensify The job is private for me. |
ah shoot - sent invite to apply! |
@dylanexpensify Applied, thank you! |
Offer sent! |
Payment done! |
Coming from #9183 (comment)
@kidroca Has raised that this workaround can be fixed in the
react-native-web
upstream and that is definitely what we prefer. Creating this issue to track a progress on this.Slack discussion is here
The text was updated successfully, but these errors were encountered: