-
Notifications
You must be signed in to change notification settings - Fork 4
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
Reprocessed Modal: Submission History #3343
Conversation
- Add ReprocessedModal component - Use new component for submission history tables
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3343 +/- ##
===========================================
- Coverage 91.61% 91.57% -0.05%
===========================================
Files 298 298
Lines 8520 8526 +6
Branches 621 621
===========================================
+ Hits 7806 7808 +2
- Misses 602 606 +4
Partials 112 112
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Fixed bug in Modal that caused it to crash when tabbing or shift tabbing with only one button
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as written! I have a suggestion regarding the structuring of the components that I would like your thoughts on before I approve, but I'll let you decide whether to move forward with it or not.
tdrs-frontend/src/components/SubmissionHistory/CaseAggregatesTable.jsx
Outdated
Show resolved
Hide resolved
tdrs-frontend/src/components/SubmissionHistory/ReprocessedModal.jsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@@ -474,4 +486,42 @@ describe('SubmissionHistory', () => { | |||
} | |||
} | |||
) | |||
|
|||
it('Shows Reprocessed button', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elipe17 do we need more tests here to capture the following scenarios:
- reprocessing tribal TANF file
- reprocessing SSP file
- no reprocessing
Asking because I noticed that reprocessing indicators are not appearing for tribal TANF and SSP files. evidence below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be the same exact logic regardless of TANF, SSP, Tribal. I just tested SSP locally and it was fine. Let me checkout the deployed env
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ADPennington I just tested in the Raft env since it is still deployed there and it is working as expected for TANF, SSP, and Tribal. Maybe we can deploy this back to qasp when you are ready and check it out together?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @elipe17 -- one thing i forgot to mention is that I was testing aggregate and stratum files for SSP and tribal TANF.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Roger. I tested active, closed, and aggregate for TANF. Active and aggregate for SPP. Only active for Tribal. Let me know when you are ready to test it out and we can hop on a call or work async via the deployment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elipe17 re-deploying now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes requested re: reprocessing on tribal and SSP files.
@ttran-hub -- do you have some time today for a11y testing for this PR? we need a11y testing on data file page > submission history tab, in the areas highlighted in the screenshot below. This branch is in qasp env. @klinkoberstar can you remind me -- is there a release note associated with this? |
a111y LGTM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 🚀 🚀
Summary of Changes
Pull request closes Reprocessed on enhancement (3014 follow-on) #3271
How to Test
List the steps to test the PR
These steps are generic, please adjust as necessary.
Reprocessed
button isn't visible in submission historyReprocessed
button is visible in submission history for the files you reparsedIn the
raft
environment use the following STT, year, and quarter to easily view the changes:Arizona Year:2021 and Quarter:1
Deliverables
More details on how deliverables herein are assessed included here.
Deliverable 1: Accepted Features
Checklist of ACs:
Deliverable 2: Tested Code
CodeCov Report
comment in PR)CodeCov Report
comment in PR)Deliverable 3: Properly Styled Code
Deliverable 4: Accessible
iamjolly
andttran-hub
using Accessibility Insights reveal any errors introduced in this PR?Deliverable 5: Deployed
Deliverable 6: Documented
Deliverable 7: Secure
Deliverable 8: User Research
Research product(s) clearly articulate(s):