-
Notifications
You must be signed in to change notification settings - Fork 8
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
Roles page for orgs #948
Roles page for orgs #948
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -35,6 +35,9 @@ const OrgLayout = () => { | |||
</NavLinkItem> | |||
))} | |||
</Sidebar.Nav> | |||
<Sidebar.Nav heading="Organization"> | |||
<NavLinkItem to="../../access">Access & IAM</NavLinkItem> | |||
</Sidebar.Nav> |
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.
unfortunately the paths here are kind of messed up and I think they depend on my RR fix and another prerelease, which we've been waiting on longer than I expected
.filter((u) => !usersInPolicy.has(u.id)) || [] | ||
) | ||
}, [users, policy]) | ||
} |
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.
Amusingly, extracting these doesn't save any lines, but the logic is weird enough and identical enough that I think they're worth sharing. Generally I like the idea of being able to treat this stuff like it's part of the API layer when we're in app
.
Closes #927
It's almost identical to the project access page, so I extracted some of the weirder bits of common logic.