-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Dashboard] Deslugging #16070
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
[Dashboard] Deslugging #16070
Conversation
started the job as gitpod-build-se-deslugging.1 because the annotations in the pull request description changed |
0df0646
to
0ead92c
Compare
@@ -232,13 +228,13 @@ export default function Menu() { | |||
) { | |||
teamSettingsList.push({ | |||
title: "Usage", | |||
link: `/t/${team.slug}/usage`, | |||
link: `/org-usage`, |
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 can align usage and org-usage in follow-up steps, same for billing/org-billing
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.
Sounds good - the /org-usage
path here felt weird to me since nothing else is prefixed by /org-
. Do you mean it'll be easier to change after this PR to something like that?
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.
It's just fewer changes. the PR is already quite big.
const entries: (ContextMenuEntry & { slug: string })[] = [ | ||
...(hasIndividualProjects | ||
const entries: ContextMenuEntry[] = [ | ||
...(!user?.additionalData?.isMigratedToTeamOnlyAttribution |
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.
with this change I'm adding the previously deprecated "personal account" entry back in the drop-down menu unless you have been migrated (in preview env everyone is migrated, so you don't see this) If you want to test the behavior you need to change the config cat value and delete/recreate your user.
0ead92c
to
6dc433f
Compare
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.
A few changes/recommendations - I did bump into what seems like a bug when dealing with multiple orgs, and refreshing the page not seeming to load the last selected org correctly, which seems worth looking into.
/werft run 👍 started the job as gitpod-build-se-deslugging.4 |
6dc433f
to
c97ba94
Compare
Thank you @selfcontained 🙏 I've fixed the reload issue and also addressed all of your feedback. |
f8c7039
to
fbe8ac6
Compare
fbe8ac6
to
e056477
Compare
Description
This change removes the team slugs and instead relies on a search param that if provided on any URL will switch the currently active org. I've decided not only add a generic redirect for old URLs (
/t/*
) under the assumption that those URLs are not (or super rarely) shared outside the app (I have no data 😇 )Attention: This is a follow up and includes the changes in #16050, you can either review all changes together or separated
Related Issue(s)
Fixes #16053
How to test
Check all navigation paths and verify they work as intended.
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-test
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh