Skip to content

Creates the `tailwind_all_the_way` feature flag

Paul Gascou-Vaillancourt requested to merge tailwind-feature-flag into master

What does this MR do and why?

Creates the tailwind_all_the_way feature flag

This creates the tailwind_all_the_way feature flag and lays the groundwork for what we'll need to take advantage of it:

  • GitLab UI utitilies are moved to their own stylesheet so that we can easily switch between the legacy library and the Tailwind one.
  • We create the "all the way" Tailwind stylesheet and config. These compile the app/assets/builds/tailwind_all_the_way.css CSS file which gets included when the feature flag is enabled. For now, this file is unreliable as it requires the second iteration where we'll create the proper CSS in Js config for Tailwind to generate our legacy utils.
  • The Tailwind compiler is updated to compile both Tailwind CSS bundles.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request reports