-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add disease specific AOE tab for bulk upload guide #8165
Conversation
); | ||
const user = userEvent.setup(); | ||
|
||
expect(screen.getAllByText("Required for Positives")).toHaveLength(1); |
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.
Required for Positives
tag in the explanation of how the tags work at the start of the guide
{ | ||
title: MULTIPLEX_DISEASES.HIV, | ||
slug: MULTIPLEX_DISEASES.HIV, | ||
items: [ |
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.
In this PR are we addressing the HIV AOE questions or just adding the disease specific AOE tabs?
Because if we want the guide to reflect what is required we should add genders of sexual partners.
Let me know what you think! 👀
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.
Just adding disease specific AOE tabs for this ticket, but #7461 is in the parking lot for adding the content for new AOE like genders of sexual partners
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.
Nice work on the implementation of this, Mike! I left a couple comments/questions for you!
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! Thank you!!
I can't tell from the original ticket, but did we want the non-relevant AOE questions for a disease to even show in that tab? e.g. |
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 thanks for your great work on this!
@mehansen I checked with Jayna and we're good to remove those AOE columns for HIV, so I just updated it here |
(unrelated to your changes @mpbrown 😅) We also have some columns like |
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! Tested locally!
@emyl3 Ooh these are great questions. We do send that data for all single-entry. IMO I think it's okay to send it and it won't hurt, but I don't know if I would categorize it as an HIV AOE question. However it's still valid data to be potentially included so maybe it does belong in the bulk upload guide somewhere? Another one potentially like that is patient sex assigned at birth. Re: the fields that we only collect for bulk upload, I wouldn't mind if we stopped collecting them because from an engineering standpoint it makes maintenance either but I'm not sure whether we have product reasons for keeping them around. cc @jayna-SkylightDigital to get her thoughts |
cfadc68
to
3e25037
Compare
Rebasing this PR for the new terraform changes, so I redeployed to dev6 and it's ready for re-review again! |
Quality Gate failedFailed conditions |
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.
🚢
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! thanks for this
export interface Item { | ||
name: string; | ||
colHeader: string; | ||
required: boolean; | ||
requested: boolean; | ||
examples?: string[]; | ||
description?: string[]; | ||
acceptedValues?: string[]; | ||
format?: string; |
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.
nice consolidation
FRONTEND PULL REQUEST
Related Issue
Changes Proposed
CsvSchemaItem
to use aRequiredStatusTag
enum instead of combinations ofrequired
andrequested
requested
in favor ofoptional
Additional Information
Testing
Screenshots / Demos