- Issue created by @scott_euser
- 🇺🇸United States cmlara
Overall looks good.
There is one small oddity I encountered in a quick validation check.
If one sets the permission for a role (such as content editor) and then sets the Authenticated user to have the permission the content editor role permission is still present so it will not display the inheritance warning, however at the same time a site owner can not remove the permission from the role as it is inherited.
While the patch is actually technically more correct as currently written, should we consider performing the inheritance check first and then the hasPermission check for a more consistent UI?
If we were to do that however I imagine the Administrator role would show as inheriting, is that a better or worse UX than what is currently in the patch?
Leaving NR for additional feedback.