Refactor protection components
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Looking at the component structure, I’d like to propose a little rewrite. Right now the protection and protection row component include all possible options for users, roles or text based rules. But without the context, it looks like they can all exist next to each other, where there’s actually no way to have a link for status check followed by a row with users’ avatars. The decision what to render is diluted, distributed across 2 components and index file. I think we can move protection row content into protection, but extract small components for 1) text base protection, 2) avatars based protection & 3) badge based protection
Edited by 🤖 GitLab Bot 🤖