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

Fleet UI: Clean up TabNav and TargetChipSelector components #26256

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

RachelElysia
Copy link
Member

@RachelElysia RachelElysia commented Feb 11, 2025

Issue

Part 1 For #26231

Description

  • TabNav and TargetChipSelector
  • See QA notes in ticket

Screenshot/screen recording

TODO: After designs are finalized

Checklist for submitter

If some of the following don't apply, delete the relevant line.

  • Changes file added for user-visible changes in changes/, orbit/changes/ or ee/fleetd-chrome/changes.
    See Changes files for more information.
  • Added/updated automated tests
  • A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it)
  • Manual QA for all new/changed functionality

Copy link

codecov bot commented Feb 11, 2025

Codecov Report

Attention: Patch coverage is 86.20690% with 4 lines in your changes missing coverage. Please review.

Project coverage is 63.66%. Comparing base (daabdb6) to head (00ed59f).
Report is 23 commits behind head on main.

Files with missing lines Patch % Lines
...iveQuery/TargetChipSelector/TargetChipSelector.tsx 78.57% 3 Missing ⚠️
frontend/components/TabText/TabText.tsx 90.90% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main   #26256   +/-   ##
=======================================
  Coverage   63.66%   63.66%           
=======================================
  Files        1631     1633    +2     
  Lines      156545   156558   +13     
  Branches     4046     4045    -1     
=======================================
+ Hits        99657    99673   +16     
+ Misses      49038    49034    -4     
- Partials     7850     7851    +1     
Flag Coverage Δ
frontend 53.57% <86.20%> (+0.07%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

import SearchField from "components/forms/fields/SearchField";
import RevealButton from "components/buttons/RevealButton";
import TargetPillSelector from "./TargetChipSelector";
Copy link
Member Author

Choose a reason for hiding this comment

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

Moved to separate directory/file to add unit tests, storybook, organize styling

}
&__tab {
padding: $pad-small 0;
padding: $pad-small 0 $pad-medium;
Copy link
Member Author

Choose a reason for hiding this comment

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

new per figma design

position: sticky;
top: 0;
background-color: $core-white;
z-index: 2;

.react-tabs {
&__tab-list {
border-bottom: 1px solid $ui-gray;
border-bottom: 1px solid $ui-fleet-black-10;
Copy link
Member Author

Choose a reason for hiding this comment

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

per figma design

@@ -34,7 +34,7 @@
}

&:hover {
box-shadow: inset 0 0 0 1px $core-vibrant-blue-over;
background-color: $ui-vibrant-blue-10;
Copy link
Member Author

Choose a reason for hiding this comment

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

changed hover state per figma design

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.

1 participant