-
Notifications
You must be signed in to change notification settings - Fork 887
fix: only show editable orgs on deployment page #14193
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
Conversation
🤖 Meticulous spotted visual differences in 528 of 1265 screens tested: view and approve differences detected. Last updated for commit ba22bc9. This comment will update as new commits are pushed. |
Also make sure the redirect from /organizations goes to an org that the user can edit, rather than always the default org.
f01285d
to
713b954
Compare
If you cannot |
Yup I want to do this, I was going to do it in a separate PR though! For now it shows an ineditable form, as before. |
Perfect 👍. Mainly just curious |
We show the org on the sidebar if they can edit anything, and we show each sub-link if they can view it, which means we were making both edit and view permission checks. Instead, show each link if they can edit it (not just view), which negates the need for separate view permissions. Incidentally, this also reduces the number of checks we need to make for individual pages, since some of them were only used on the sidebar.
92d15c5
to
475f6e2
Compare
The new summary page: #14214 Kinda sad and sparse looking but hopefully better than an ineditable form 😛 |
caf0649
to
83bf388
Compare
site/src/pages/ManagementSettingsPage/OrganizationSettingsPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/OrganizationSettingsPage.test.tsx
Outdated
Show resolved
Hide resolved
1d95c86
to
64631e1
Compare
5d9378b
to
ba22bc9
Compare
Also make sure the redirect from /organizations goes to an org that the user can edit, rather than always the default org.