Skip to content
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

Make Label Cursor Hoverable #3332

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

YuliaKrimerman
Copy link
Contributor

https://issues.redhat.com/browse/RHOAIENG-13047

Description

Made the labels indicate they are hoverable in Settings page

Screen.Recording.2024-10-14.at.3.47.21.PM.mov

How Has This Been Tested?

On the UI

Test Impact

Request review criteria:

Self checklist (all need to be checked):

  • The developer has manually tested the changes and verified that the changes work
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

  • Included any necessary screenshots or gifs if it was a UI change.
  • Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

  • The developer has tested their solution on a cluster by using the image produced by the PR to main

Copy link
Contributor

openshift-ci bot commented Oct 14, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign manosnoam for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

@manaswinidas manaswinidas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the label should only be hoverable for "Unavailable" and any other labels where we are showing a popover. There are no actions for "Available" and "Progressing" AFAIR - so no use making it hoverable(and confusing the users). Also, I think it's a bad practice to use void 0(makes it inaccessible for screen readers- reference link) Can we use a button instead? - I think button is hoverable by default.

Copy link

codecov bot commented Oct 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.82%. Comparing base (ae66e3b) to head (10bc6e3).
Report is 3 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #3332      +/-   ##
==========================================
+ Coverage   84.80%   84.82%   +0.02%     
==========================================
  Files        1315     1315              
  Lines       29491    29499       +8     
  Branches     8056     8063       +7     
==========================================
+ Hits        25009    25024      +15     
+ Misses       4482     4475       -7     
Files with missing lines Coverage Δ
...elRegistrySettings/ModelRegistryTableRowStatus.tsx 98.86% <100.00%> (+0.09%) ⬆️

... and 7 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ae66e3b...10bc6e3. Read the comment docs.

@YuliaKrimerman
Copy link
Contributor Author

@manaswinidas Made it hoverable only for the 2 needed statuses. Kept it as Label because of the color prop vs button. addressed the void 0 issue as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants