-
Notifications
You must be signed in to change notification settings - Fork 924
chore: apply design changes to the admin settings menu dropdown #15947
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
Changes from all commits
67b8927
4606d3a
fa0aec1
c009fc7
dcd3e79
a3b59d3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,13 +2,14 @@ import { type Interpolation, type Theme, css, useTheme } from "@emotion/react"; | |
import Button from "@mui/material/Button"; | ||
import MenuItem from "@mui/material/MenuItem"; | ||
import { DropdownArrow } from "components/DropdownArrow/DropdownArrow"; | ||
import { FeatureStageBadge } from "components/FeatureStageBadge/FeatureStageBadge"; | ||
import { | ||
Popover, | ||
PopoverContent, | ||
PopoverTrigger, | ||
usePopover, | ||
} from "components/deprecated/Popover/Popover"; | ||
import { linkToAuditing, linkToUsers } from "modules/navigation"; | ||
import { linkToAuditing } from "modules/navigation"; | ||
import type { FC } from "react"; | ||
import { NavLink } from "react-router-dom"; | ||
|
||
|
@@ -52,7 +53,7 @@ export const DeploymentDropdown: FC<DeploymentDropdownProps> = ({ | |
/> | ||
} | ||
> | ||
Administration | ||
Admin settings | ||
</Button> | ||
</PopoverTrigger> | ||
|
||
|
@@ -81,7 +82,6 @@ export const DeploymentDropdown: FC<DeploymentDropdownProps> = ({ | |
const DeploymentDropdownContent: FC<DeploymentDropdownProps> = ({ | ||
canViewDeployment, | ||
canViewOrganizations, | ||
canViewAllUsers, | ||
canViewAuditLog, | ||
canViewHealth, | ||
}) => { | ||
|
@@ -98,7 +98,7 @@ const DeploymentDropdownContent: FC<DeploymentDropdownProps> = ({ | |
css={styles.menuItem} | ||
onClick={onPopoverClose} | ||
> | ||
Settings | ||
Deployment | ||
</MenuItem> | ||
)} | ||
{canViewOrganizations && ( | ||
|
@@ -109,16 +109,7 @@ const DeploymentDropdownContent: FC<DeploymentDropdownProps> = ({ | |
onClick={onPopoverClose} | ||
> | ||
Organizations | ||
</MenuItem> | ||
)} | ||
{canViewAllUsers && ( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I worry that this is going to be one of those things that customers with lots of screenshots will really dislike. Can we loop @bpmct in on this so we can communicate this change clearly and hopefully mitigate frustrations? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ideally, the figma designs would already have been reviewed to validate this type of change. Almost everything about this PR would change existing screenshots. We should converge on a process after the holidays so we don't have to worry about these types of changes during PR review. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah but changing things stylistically is very different from removing a path that users are accustomed to and have documented. I doubt customers care nearly as much when things look slightly different but have the same structure as they do when we remove the button they put a screenshot of in their documentation entirely. |
||
<MenuItem | ||
component={NavLink} | ||
to={linkToUsers} | ||
css={styles.menuItem} | ||
onClick={onPopoverClose} | ||
> | ||
Users | ||
<FeatureStageBadge contentType="beta" size="sm" showTooltip={false} /> | ||
</MenuItem> | ||
)} | ||
{canViewAuditLog && ( | ||
|
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.
also, how can we track that this actually gets cleaned up later?
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.
We could create an issue but im not sure its worth the trouble. This will get resolved automatically either when the beta badge is removed or this component moves to the new popover. The issue is that the current popover does not work well when it appears too close to the right edge of the screen.