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
update Installed Operators empty state #1671
update Installed Operators empty state #1671
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.
/lgtm
/retest Please review the full test history for this PR and help us cut down flakes. |
Can you confirm that this doesn't hide the filter bar if you deselect all row filters with items? Otherwise you couldn't clear the filter. /hold |
frontend/public/components/operator-lifecycle-manager/clusterserviceversion.tsx
Show resolved
Hide resolved
@spadgett I put an example of this working below. |
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
/hold cancel |
7b313dc
to
395e8ac
Compare
/retest |
395e8ac
to
10b2528
Compare
Since we can display entirely different messages, I'd say something like "No Operators match filter" or similar. (Someone from the design side can probably recommend a better message.) |
@tlwu2013 Do you have any suggestions? |
1a7d143
to
69db6a9
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.
Code looks good, and the removed tests no longer directly apply because the filter bar is no longer visible in these scenarios. Let's open a follow on issue to improve test coverage of custom resources.
/lgtm
@@ -42,6 +42,11 @@ | |||
font-size: 13px; | |||
} | |||
|
|||
.co-clusterserviceversion-empty__state__namespace { | |||
font-weight: bold; | |||
font-style: italic; |
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.
nit: alphabetize
/retest Please review the full test history for this PR and help us cut down flakes. |
It looks like the OLM integration test errors are legimitate, and PR needs rebase. /hold |
69db6a9
to
34a309d
Compare
34a309d
to
7d9e3fb
Compare
@nicolethoen fyi, conflict in list-page.jsx |
7d9e3fb
to
1023c73
Compare
/retest |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtaylor113, nicolethoen, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@@ -170,15 +169,6 @@ describe('Interacting with an `AllNamespaces` install mode Operator (Redis)', () | |||
expect(crudView.successMessage.getText()).toContain(`${redisEnterpriseCluster} has been updated to version`); | |||
}); | |||
|
|||
it('displays Kubernetes objects associated with the `RedisEnterpriseCluster` in its "Resources" section', async() => { |
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.
This test is the one that needs to be readded once the RedisCluster is adjusted - currently there are no kubernetes objects being created to display in the resources section so this test was not failing because of my change - my change actually highlighted the issue. It had not been effectively testing this scenario before hand.
addresses CONSOLE-1466