-
Notifications
You must be signed in to change notification settings - Fork 894
fix: ensure user admins can always see users table #15226
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 1 commit
1ad09fa
620bd3a
7ee3cf0
e889621
36e0376
032a75c
eea8bbd
e6d4201
14fc68e
a8fd9e6
0a36cd1
e6d772b
3752af5
2068a4c
2fe3d53
3c41de0
162642e
64c6f29
e12a4aa
b9b33c0
f7df5ff
6925294
9fc0afa
498e7ba
234c606
4496a75
9fcf3e7
19fb6e5
804255e
d341175
f3e6659
ce67a66
7e946a7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -426,16 +426,24 @@ export const router = createBrowserRouter( | |
</Route> | ||
</Route> | ||
|
||
{/** | ||
* @todo 2024-10-24 - MES - The current deployment page is | ||
* almost empty, which isn't great for two reasons: | ||
* | ||
* 1. Even though none of our links lead to the page, the | ||
* user is still able to navigate straight there by | ||
* accident. | ||
* 2. If the user has access to some deployment pages, but | ||
* tries accessing one that they shouldn't be able to | ||
* access, we have to reroute them somewhere. The base | ||
* deployment route is the only safe option, because not | ||
* even the general page is accessible by everyone. | ||
* | ||
* Should update the base /deployment page so that there's | ||
* something there, but that will require coordination with | ||
* the design team. | ||
*/} | ||
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 really wish I could've added some content here, but it felt really out of scope. At the very least, better a janky experience over a broken one 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. Maybe something to think together with @chrifro |
||
<Route path="/deployment" element={<ManagementSettingsLayout />}> | ||
{/* | ||
None of the UI elements link directly to the base | ||
/deployment route, but if you navigate there directly, | ||
you would just see a mostly empty screen. Redirect to | ||
the general page for better UX. */} | ||
<Route | ||
path="" | ||
element={<Navigate to="/deployment/general" replace />} | ||
/> | ||
<Route path="general" element={<GeneralSettingsPage />} /> | ||
<Route path="licenses" element={<LicensesSettingsPage />} /> | ||
<Route path="licenses/add" element={<AddNewLicensePage />} /> | ||
|
Uh oh!
There was an error while loading. Please reload this page.