-
Notifications
You must be signed in to change notification settings - Fork 1
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
CRDCDH-1995 Validation Results Aggregated/Expanded Table Views #557
Conversation
…, and populating the issueType filter
Pull Request Test Coverage Report for Build 12813170611Details
💛 - Coveralls |
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 tested it locally as best as I could and annotated a few comments. Feel free to dismiss any.
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.
Changes LGTM!
Everything seems to work, except the type filter and expand button (as noted). Feel free to merge when verified against the finished API.
@Alejandro-Vega It looks like Jest keeps failing (I tried rerunning it too). Could you check and see if it's related to these changes? |
Oops, thanks for catching that I forgot to rerun them at the end. I went ahead and fixed them in 136264d. Also FYI, I did find one additional issue on the BE for Data File related errors. Their codes are returning null, but the Metadata related error codes are populated correctly. Still should be fine to merge though. |
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.
All the changes still LGTM and it seems to work as expected.
I annotated a suggestion to skip the queries for the hidden filters when viewing aggregated view, which saves 3 network requests initially. The only downside is, when you toggle between aggregated/expanded, it will re-execute the queries every time instead of just once on mount (current implementation).
I'm unsure if it's worth the tradeoff, since I don't know how often people will switch between the views. With that being said, I'll defer to you for the decision on this.
Overview
Added Aggregated/Expanded view to the table in Validation Results tab in a Data Submission.
Note
The BE currently does not populate issue codes. (They all return as null) which breaks some functionality such as the issue type filter, "Expand" and button. There is also a BE bug when passing -1 for the "first" param of the aggregated submission QC results API.
Change Details (Specifics)
Related Ticket(s)
CRDCDH-2037 (Aggregated View Task)
CRDCDH-1995 (Expanded View Task)
CRDCDH-1889 (US)