-
Notifications
You must be signed in to change notification settings - Fork 29
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
refactor: 💡 use hds side nav w/ hds frame instead of rose #2688
base: llb/side-nav-refactor
Are you sure you want to change the base?
refactor: 💡 use hds side nav w/ hds frame instead of rose #2688
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 looks incredible!
{{/if}} | ||
</Rose::Nav::Sidebar> | ||
{{#if this.session.isAuthenticated}} | ||
{{#in-element this.sideBarContainer}} |
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 did we have to portal this in?
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.
thats a good point, i think the same thing can be accomplished using the side nav list directly.
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.
Edit: Just realized you are referring to the in-element
helper usage. That is because we don't show the side nav on all routes but we do want the side nav to be inserted into the correct hds::frame component.
e30d653
to
0583534
Compare
@@ -53,3 +53,20 @@ form { | |||
color: inherit; | |||
} | |||
} | |||
|
|||
// TODO: This is a temporary fix that ensures changing the color theme won't alter the dropdown colors. | |||
.hds-app-frame__sidebar .hds-side-nav { |
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.
Hds team is helping us find a cleaner solution for this style override. So this fix is just temporary.
@@ -37,7 +37,7 @@ | |||
<page.actions> | |||
{{#if (or perms.canUpdate perms.canDelete)}} | |||
|
|||
<Hds::Dropdown as |dd|> | |||
<Hds::Dropdown data-test-manage-alias as |dd|> |
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.
Do we want to specify that this is the manage alias dropdown in the targets route?
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.
ah great point!
const DROPDOWN_BUTTON_SELECTOR = | ||
'tbody tr td:last-child .hds-dropdown-toggle-icon'; |
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.
asking for learning: Did this need to be updated since we have more dropdown (specifically in the new side nav) elements on the screen? Either way, I think this is a good change.
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.
yup that is correct!
Description
Refactor to use
Hds::SideNav
andHds::AppFrame
components.Note: There is an issue with the
Hds::SideNav::List
component so we are using theHds::SideNav::Portal
component in the meantime.The side nav should not be visible on the
onboarding
,change-password
, andauthenticate
routes.Screenshots (if appropriate)
How to Test
a. user menu options such as sign-out, change-password, light mode, dark mode, etc.
b. dev tool toggle options such as feature editions and licensed features.
Checklist