Remove 100% of calls to bootstrap components in haml files by utilizing GitLab UI components for modals, popovers, tooltips, tabs, dropdowns, pagination, buttons, and alerts
Christopher Lefelhoczchanged title from KR: Remove 100% of calls to bootstrap components in haml files by utilizing GitLab UI components for modals, popovers, tooltips, tabs, dropdowns, pagination, buttons, and alerts to KR: Migrate HAML components to Pajamas
changed title from KR: Remove 100% of calls to bootstrap components in haml files by utilizing GitLab UI components for modals, popovers, tooltips, tabs, dropdowns, pagination, buttons, and alerts to KR: Migrate HAML components to Pajamas
@timzallmann / @samdbeckham - The groupthreat insights frontend team wants to help support this KR. We've created the following two KRs for Q3 & would appreciate your guidance on how best to start contributing to this HAML migration:
Thanks folks. I started tracking these in gitlab-org&3963 (closed) . In the epic, there are sub-epics that list all the instances of bootstrap components in HAML as seperate issues. They're arranged by component and we've identified buttons and alerts so far. I'm working on pagination right now and will move on to identifying the others shortly. If your teams could look in to those and start picking off some of the issues that will go a long way in helping out this effort.