-
Notifications
You must be signed in to change notification settings - Fork 0
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
base: 3.2.0
Are you sure you want to change the base?
Conversation
…, and populating the issueType filter
Pull Request Test Coverage Report for Build 12589515921Details
💛 - 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.
// "All" is the default selection for all filters | ||
expect(mockMatcher).not.toHaveBeenCalledWith( | ||
expect.objectContaining({ batchIDs: expect.anything(), nodeTypes: expect.anything() }) | ||
); | ||
expect(mockMatcher).toHaveBeenCalledWith(expect.objectContaining({ severities: "All" })); | ||
// TODO: FIX TEST | ||
// expect(mockMatcher).toHaveBeenCalledWith(expect.objectContaining({ severities: "All" })); |
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.
Is this a TODO for when the API works, or is this broken due to ACT/etc?
Just pointing this out in case it was forgotten. If it is an ACT issue, feel free to leave it commented out. Tracing the root cause for act is a nightmare 😃
const handleFilterChange = (field: keyof FilterForm) => { | ||
setTouchedFilters((prev) => ({ ...prev, [field]: true })); | ||
}; | ||
|
||
const Actions = useMemo<React.ReactNode>( |
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.
Currently, the export button is only exporting the QC Results. I think the expectation would be that it exports the Aggregated Results when that's selected? I could be wrong.
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)