-
Notifications
You must be signed in to change notification settings - Fork 17
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
Cheek Samples #334
base: master
Are you sure you want to change the base?
Cheek Samples #334
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 assume this may change a little because of the private-api refactor, but I have no concerns about the current contents, just a couple of questions.
"Mouth", "Nares", "Nasal mucus", "Right hand", | ||
"Left hand", "Forehead", "Torso", "Right leg", | ||
"Left leg", "Vaginal mucus", "Tears", "Ear wax", | ||
"Hair", "Fur"] |
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.
No request for changes here, just a question: how are these entries ordered?
$("#sample_site_last_washed_date").val(""); | ||
$("#sample_site_last_washed_time").val(""); | ||
$("#sample_site_last_washed_product").val("").change(); | ||
} |
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'm a little surprised that sample_site_last_washed_date_normalized
isn't also blanked out at the same time, for the potential case where the user initially sets something as a cheek sample but then changes it. Or is that case handled at submission by the monthDayYearCheekWash
validation?
This PR is intended to address the needs surrounding collecting skin samples from cheeks:
It adds Cheek as a valid sample site to the user interface.
It adds the necessary UI components to support barcode metadata, which is explained conceptually in the corresponding microsetta-private-api PR at Cheek Samples #334
One note - integration tests will fail until the corresponding microsetta-private-api is merged into master. Unless there's a reason to do otherwise, I'd like to proceed with static code review, then revisit any necessary tweaks to the integration tests via supplemental code review if needed.