-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2024-10-25] Migrate changes in react-native-qrcode-svg-old
to react-native-qrcode-svg
#47711
Comments
Triggered auto assignment to @bfitzexpensify ( |
cc @Kicu - Do you think someone else from SWM would be interested in looking into this? Otherwise I can extend out to one of our other agencies |
react-native-qrcode-svg-old
to react-native-qrcode-svg
Current assignee @bfitzexpensify is eligible for the NewFeature assigner, not assigning anyone new. |
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
Not really a bug not really a new feature... more of an improvement |
Because Expensify is now the owner of this open source library I think we should try to keep commits and PRs clean and self contained. Because of this my suggestion would be to migrate the two PRs that we did on the original fork separately:
If we do that, then later when testing or if anything breaks we can easily revert the svg code, while the example app should stay as it helps with development a lot. I can migrate the two separately and open them on https://github.com/Expensify/react-native-qrcode-svg/ |
Agree with that. Let's do it. |
PR that adds the Example app: Expensify/react-native-qrcode-svg#206 Will followup soon with another PR that adds the SVG changes that we need in Expensify App |
I also have the SVG changes nicely cleaned up with like 2 extra commits locally, so I will open the 2nd PR with the SVG code on Monday, and this issue should be solved :) |
Nice! Thank you ❤️ |
Thank you @Kicu ! |
I pinged someone to look into the branch rules for the new repo, hopefully we can get this fixed soon. |
Since you are back, I'll unassign myself @bfitzexpensify |
@luacmartins do you have an update on #47711 (comment) |
Yea, we solved the branch rules but now we have the npm auth issue we were discussing in Slack |
bumped in slack |
Is there any way I can help with this one? |
It seems like we still have permissions issues with npm. Asking infra if they have npm package access so we can update the permissions |
We published the latest version 6.3.11 to npm. Let's update App. |
nice 👍 I can take care of that |
@luacmartins @grgia this PR updates the version in |
react-native-qrcode-svg-old
to react-native-qrcode-svg
react-native-qrcode-svg-old
to react-native-qrcode-svg
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.50-8 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 2024-10-25. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
This is back-end work that QA won't touch, so I don't see the need for a regression test. Payment not needed. Closing this out. |
See https://expensify.slack.com/archives/C01GTK53T8Q/p1724159312329299?thread_ts=1697098846.087309&cid=C01GTK53T8Q
Background
Goal
Issue Owner
Current Issue Owner: @bfitzexpensifyThe text was updated successfully, but these errors were encountered: