Implement PDF Generation side sheet. - #12619
Conversation
|
Size Change: +1.4 kB (+0.06%) Total Size: 2.3 MB 📦 View Changed
ℹ️ View Unchanged
|
eugene-manuilov
left a comment
There was a problem hiding this comment.
Thanks, @benbowler. Left some feedback for you. Please, take a look.
aaemnnosttv
left a comment
There was a problem hiding this comment.
Thanks @benbowler ,
I've left a few additional comments of my own here while being pulled in on the review.
One additional important point which hasn't been raised is that all new files and components should be authored in TypeScript (unless there is a good reason we can't), but everything here has been added in JS.
The key lines in the code you copied are: This PR is a stub that doesn't require the implementation of the datastore. The core forms will be replaced with the correct PDF generation state within #12537 and beyond. |
If #12537 is a dependency for this ticket, we should start with that task first, or not?
#12537 only says to extend the existing widgets infrastructure to support PDF variants. I don't see it mentioning creating a PDF-specific datastore to handle the PDF generation state. |
…pdf-generation-button-and-sidesheet.
|
@eugene-manuilov I've created the missing datastore ticket (let's prioritise reviewing this and getting it into the next sprint) and addressed the code review comments. |
eugene-manuilov
left a comment
There was a problem hiding this comment.
Thanks, @benbowler. There are VRT issues. Could you please take a look? Once fixed, please, assign to @aaemnnosttv for review as well. I have nothing else to add 👍.
…pdf-generation-button-and-sidesheet.
|
Remaining VRT failure and E2E failures are unrelated to this work. |
aaemnnosttv
left a comment
There was a problem hiding this comment.
Thanks all! I pushed a few extra fixes to get this over the line
DashboardMainApphad a complexity over the limit. There is a lot of room for improvement in this component but I made the smallest change necessary; we can address further improvements in a new issue.- Test failures related to focus trap – seems related to an odd nuance about our tabbable mock not being applied in all instances
- Refactored the use of form state to use the new
useFormValuehook for consistency (also a bit cleaner) + fixed one instance of this which was broken by the update
Summary
Addresses issue:
Relevant technical choices
PR Author Checklist
Do not alter or remove anything below. The following sections will be managed by moderators only.
Code Reviewer Checklist
Merge Reviewer Checklist