-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix Checks results filters #1073
Conversation
16bb89f
to
13afe6f
Compare
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.
Hey @jamie-suse ,
The code looks great! Thank you for adding tests ;)
I would appreciate a gif to see it working
error, | ||
expectations, | ||
failedExpectations, | ||
result: health, |
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.
Why this change from health
to result
?
We use health
all around the frontend code.
Is it because the predicate
function expects that?
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.
Yep that's correct, predicate()
relies on result
being present.
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
Description
Fixes changes to the new checks results filters from bd2f538.
Fixes #1064
How was this tested?
Added new tests for filtering in
ExecutionResults.test.jsx
.