-
Notifications
You must be signed in to change notification settings - Fork 3
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
Cmdct 4229 - pre-populate drawer with plans #11995
Conversation
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.
I like how you were able to reuse the ilos logic! I have some questions:
Other than the comment I added, I agree with all of @gmrabian's comments above! This is looking really good, we just need to clean up a couple of things 😄 |
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's been real
one idea for cleanup 🧹
Code Climate has analyzed commit 72799e7 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 97.2% (90% is the threshold). This pull request will bring the total coverage in the repository to 96.7% (0.0% change). View more on Code Climate. |
Description
The main goal here is to populate the list of plans that appears when you go into a drawer in the analysis methods page in a NAAAR report. The logic to do so already existed for ILOS so this is my attempt to generalize that functionality.
Related ticket(s)
CMDCT-4229
How to test
Create a MCPAR report, add a plan, add an ILOS, go to section D -> ILOS, enter the plan, answer 'yes', see the ilos appears.
Create a NAAAR report, add a plan, go to the analysis methods page and enter one of them, answer 'yes', see the plan appears under the frequency question and radio button options. See that it is the same when adding a new analysis method.
Notes
Pre-review checklist
Pre-merge checklist
Review
Security
If either of the following are true, notify the team's ISSO (Information System Security Officer).
convert to a different template: test → val | val → prod