Skip to content

Prevent re-introduction of legacy utils without tailwind equivalents

Lukas 'ai-pi' Eipert requested to merge leipert-ensure-that-tailwind-equivalents-has-all-classes into master

What does this MR do and why?

Prevent re-introduction of legacy utils without tailwind equivalents

This adds a simple linter which checks that there are no legacy utils being re-introduced without us having them defined in tailwind_equivalents.json.

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

N/A

How to set up and validate locally

  1. Introduce a util which currently is not mapped in tailwind_equivalents.json
  2. Run rm -rf config/helpers/tailwind/css_in_js.js && scripts/frontend/compare_css_util_classes.mjs

Alternatively look at:

Edited by Lukas 'ai-pi' Eipert

Merge request reports