-
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 2024-04-05] Convert internal PDF preview into a public library #22998
Comments
Hi, @allroundexperts!
Thank you! |
Hi @rezkiy37! |
What is the repository name? I can get one made with correct permissions. Thank you |
@AndrewGable, are you able to create a repository within Expensify organisation? |
We haven't considered names yet. I believe |
Agreed! |
Triggered auto assignment to @nathanmetcalf ( |
Job added to Upwork: https://www.upwork.com/jobs/~01f329b3f580153b04 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @s77rt ( |
@nathanmetcalf - Please create an public Expensify repository named We will publish under npm under |
Can I please have a licence type, and a Description for this new repo? |
Otherwise, I've created it. I'm not sure what permissions if any we need. |
@nathanmetcalf, do you mean this? If yes, I will prepare and post text. |
MIT license please, can we leave the description blank for now? If not, just saying: |
@nathanmetcalf, I am not able to fork the repo, because it is empty entirely. Could someone push at lease 1 commit there? |
Looks like we will have to wait for @nathanmetcalf to fix this as I don't have permission to push to |
What permissions should be granted to this repo? I don't think we want to leave it open to everyone? |
External developers would work with own forks. Internal developers would follow your internal rules and approaches. |
@nathanmetcalf - Same permissions as App or Bedrock. Open source read, write for any internal employees. |
We will probably need the Expensify.cash OSS bots too. |
@nathanmetcalf - Can you change default branch to https://github.com/Expensify/react-fast-pdf/tree/main - there is a commit now, try to fork please @rezkiy37 |
I've forked successfully 👍 |
Thanks Andrew, I've added Expensify.cash OSS bots, and set the default branch to main. Please reopen this if there is anything further you need :) |
|
The last exected PR was merged. We finally connected the package to the app. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 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-04-05. 🎊 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:
|
@allroundexperts Will you handle the above checklist as you reviewed the linked PR? |
This was a new feature so a checklist is not needed here. However, I propose the following regression test:
Do we 👍 or 👎 ? |
@allroundexperts Can you define the minimum size for the PDF? Or to be more specific to test this case. Thanks |
@mountiny Updated! |
I reviewed the following PRs as part of this ticket: Expensify/react-fast-pdf#1 The first two I think were during the time we were paying 1k per bug / review. |
@allroundexperts @rezkiy37 Just to make sure are we all done here in terms of the steps we planned for the library? if this ready to pay out and close? |
I think yes, we're done here. @rezkiy37 can confirm though. |
Yes. The idea was to share the bugfix with the community. The package inherits the previous app behavior with all fixes and improvements. I would say that the 1st version of We are done with this issue. |
Thank you, the payment summary would be: Expensify/react-fast-pdf#1 - $1000 So $4000 to @allroundexperts for their work on this project with @rezkiy37 its taken a long time and many hours of testing and review so I think this is reasonable. |
cc @anmurali |
Payment Summary
BugZero Checklist (@anmurali)
|
Per #22998 (comment)
|
I'm not due payment here. This can be closed |
I believe @allroundexperts will be handled in newdot then, so closing, thanks everyone! |
$4,000 approved for @allroundexperts |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Actually, the Expensify app already uses react-pdf to preview PDF files. However, it does not support the large PDF files. The idea is to create, own and maintain a package. It should support the large PDF files. It is helpful to the community, if the package can be widely used for performance improved PDF viewer. The Expensify application uses the package instead of an internal implementation.
Actual Result:
This is an internal implementation. Recently, we fixed and improved the previewing of large PDF files, directly updating our own codebase - #22760.
Workaround:
The user still can use Expensify without this being fixed.
Area issue was found in:
I was found during the investigating/fixing the next issue - #19918.
Failed WCAG checkpoints
N/A
User impact:
It does not affect the user. It has an impact on the community.
Suggested resolution:
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: N/A
Reproducible in staging?: N/A
Reproducible in production?: N/A
Email or phone of affected tester (no customers): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
N/A
Expensify/Expensify Issue URL: N/A
Issue reported by: Mykhailo Kravchenko - Callstack
Slack conversation: N/A
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @anmuraliThe text was updated successfully, but these errors were encountered: