Skip to content

chore: consolidate ManageSettingsLayout code #14885

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

Merged
merged 17 commits into from
Oct 3, 2024
Merged

chore: consolidate ManageSettingsLayout code #14885

merged 17 commits into from
Oct 3, 2024

Conversation

aslilac
Copy link
Member

@aslilac aslilac commented Sep 30, 2024

Clean up a bunch of tangles that only existed to service the "multi-organization" experiment, which has now been removed

Notably, the DeploySettingsLayout component has been folded into ManagementSettingsLayout since they're both for controlling state in the "same part" of the app, one just needed to also exist outside of orgs. No longer needed!

@aslilac aslilac requested review from jaaydenh and Parkreiner October 2, 2024 17:11
<header>
<h2 css={styles.sidebarHeader}>Deployment</h2>
</header>
{showOrganizations && (
Copy link
Contributor

Choose a reason for hiding this comment

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

Why would showOrganizations need to be true to show only the Deployment header? Is there some reason to show DeploymentSettingsNavigation without the Header text?

Copy link
Member Author

Choose a reason for hiding this comment

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

it just looks weird for it to say deployment twice without the organizations section below. it's weird, but we'll get rid of this when we adopt the designs we went over with Christin.

Copy link
Member

@Parkreiner Parkreiner 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 this looks good. Just want to get confirmation on the redirect logic before I approve, to make sure it is working as intended

@@ -102,7 +102,7 @@ const UsersPage: FC = () => {
authMethodsQuery.isLoading ||
groupsByUserIdQuery.isLoading;

if (showOrganizations && location.pathname !== "/deployment/users") {
if (location.pathname === "/users") {
Copy link
Member

Choose a reason for hiding this comment

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

Could I get more context on this change? Mainly wondering why we went from !== to ===

Copy link
Member Author

Choose a reason for hiding this comment

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

The goal is just to always redirect from /users to /deployment/users. I guess I could've left it the other way, this just feels clearer to me.

Copy link
Contributor

@jaaydenh jaaydenh left a comment

Choose a reason for hiding this comment

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

Overall, looks good, I think it would be useful to add to description of the PR more details about, why deploySettings and organizationSettings were combined into ManagementSettings.

@aslilac aslilac enabled auto-merge (squash) October 3, 2024 22:00
@aslilac aslilac merged commit 8b6a06d into main Oct 3, 2024
27 checks passed
@aslilac aslilac deleted the lilac/anger branch October 3, 2024 22:00
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants