[Bugfix:TAGrading] Add Missing PDFjs Assets#12997
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12997 +/- ##
=========================================
Coverage 21.41% 21.41%
Complexity 10002 10002
=========================================
Files 277 277
Lines 37418 37418
Branches 512 512
=========================================
Hits 8013 8013
Misses 28904 28904
Partials 501 501
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
dagemcn
left a comment
There was a problem hiding this comment.
I was able to verify that the pdf would not render correctly on main and after a vagrant destroy and up the pdf would render correctly. To clarify, in the PR description you say that these packages were not installed prior, but in the code you are just copying them. Are we actually installing new dependencies here? If so, they should be added to the proper documentation. Other than that, solid work on this PR, looks good!
|
Sorry, I meant copied. The files already exist in |
Why is this Change Important & Necessary?
Fixes #12764
As of PDFjs 5.x, new assets are required for pdf rendering including wasm, iccs, and standard_fonts. These are not currently copied, resulting in failure of pdf rendering.
What is the New Behavior?
Before change (image on right):

After change:

What steps should a reviewer take to reproduce or test the bug or new feature?
Verify before behavior (on main):
Verify after behavior (on branch):
Automated Testing & Documentation
No automated testing added
Other information
Not a breaking change
No migration changes
Not a security concern