-
Notifications
You must be signed in to change notification settings - Fork 30
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
updated assurance and compliance for mmis #4519
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4519 +/- ##
==========================================
- Coverage 94.33% 93.94% -0.39%
==========================================
Files 253 252 -1
Lines 7886 7977 +91
Branches 1686 1705 +19
==========================================
+ Hits 7439 7494 +55
- Misses 428 461 +33
- Partials 19 22 +3
Continue to review full report at Codecov.
|
See this pull request in action: https://ec2-3-210-243-7.compute-1.amazonaws.com |
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.
Everything works as expected after creating a new MMIS APD!
At first I checked the one created with seed data and either we need to update the seed data or there was just some old data in the database in this environment. It looked like 45 CFR Part 92.36 was on the list instead of the desired "45 CFR Part 75.326". Also, some of the citations are just text and not links:
- 45 CFR Part 92.36
- 42 CFR Part 433.112(b)(5)-(9)
- 45 CFR Part 95.617
I just had the one question about the switch statement, but everything else looks great!
@@ -98,6 +119,8 @@ const AssurancesAndCompliance = ({ | |||
return complyingWithSecurity(index, newValue); | |||
case 'softwareRights': | |||
return complyingWithSoftwareRights(index, newValue); | |||
case 'independentVV': |
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 looks like this case is identical to the one on line 139. Are they supposed to be the same? If so I wonder if you can combine them
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.
they are updating the apd when the user selects yes and no and when the user adds a justification, so I don't think they can be combined easily
@amyd11 great catch on the regulations, I went back and I think I got them all cleaned up. |
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.
Thanks for updating the seed files! Looks good ✅
Looks good to me pending the 2 changes requested above!
|
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.
Looks good to me!
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.
Citations have been updated successfully for MMIS. Great job!
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 for the review request. Good to move forward @thetif
Resolves #4473
Description
Updated the Assurance and Compliance components to handle MMIS data. Removed some old code that creates citations on the front end if they don't already exist in the APD. This isn't needed any more because all of the APDs in staging and prod have assurance and compliance. They get added when you create and new APD. And it would be extra complicated to update it to handle the new types. Also created storybook stories.
Automated test cases written
Steps to manually verify this change
This pull request is ready to code review when
tests, refactor
This pull request is ready to test when
This pull request is ready to review when the QA has
This pull request can be merged when