Skip to content
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

🐛 Identified risk refactor #1521

Merged
merged 4 commits into from
Nov 8, 2023

Conversation

ibolton336
Copy link
Member

@ibolton336 ibolton336 commented Nov 6, 2023

@ibolton336 ibolton336 force-pushed the identified-risk-refactor branch from ffeb865 to d89d621 Compare November 6, 2023 20:55
Copy link

codecov bot commented Nov 6, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (521be72) 40.70% compared to head (224fc14) 40.70%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1521   +/-   ##
=======================================
  Coverage   40.70%   40.70%           
=======================================
  Files         145      145           
  Lines        4589     4589           
  Branches     1076     1076           
=======================================
  Hits         1868     1868           
  Misses       2707     2707           
  Partials       14       14           
Flag Coverage Δ
client 40.70% <ø> (ø)
server ∅ <ø> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ibolton336 ibolton336 force-pushed the identified-risk-refactor branch from bea6cba to 08df3d1 Compare November 7, 2023 00:11
Copy link
Member

@sjd78 sjd78 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't test the table render with the one questionnaire I have locally -- the dreaded hack/import-questionnaire/cloud-native.yaml! Seems like this report table has some issues with questions that repeat across sections.

The code looks good, I just couldn't test it.

Comment on lines 46 to 47
item.question === question.text &&
item.answer === answer.text &&
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this will have the same problem of if an assessment has repeated questions / answers right?

Maybe building up a key based on the order fields would be better?

itemId = [
  assessment.id,
  section.order,
  question.order,
  answer.order,
].join(".");

@ibolton336 ibolton336 force-pushed the identified-risk-refactor branch from 1e1c79e to 9ae0e7e Compare November 7, 2023 21:46
@ibolton336
Copy link
Member Author

I couldn't test the table render with the one questionnaire I have locally -- the dreaded hack/import-questionnaire/cloud-native.yaml! Seems like this report table has some issues with questions that repeat across sections.

The code looks good, I just couldn't test it.

Addressed this bug here: #1524

Copy link
Member

@sjd78 sjd78 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants