tailwind-ppx
tailwind-ppx copied to clipboard
A Reason/OCaml Pre-Processor eXtension (PPX) that validates your Tailwind classes at compile-time.
Linting js files inside js / workflows on pr #122
We have a few JS files in the project with no associated formater/linter, so let's add one.
Per [Manas's comment](https://github.com/dylanirlbeck/tailwind-ppx/pull/126#issuecomment-683420878), we should be able to do use the latest version of esy in CI but enforce that `rewritePrefix` is true. cc @tatchi
Right now, users of the ppx have to do `@dylanirlbeck/tailwind-ppx/tailwind-ppx`. Instead, I'd like the path to be `@dylanirlbeck/tailwind-ppx/ppx` (or `../ppx.exe` for Windows).
Per some [good](https://github.com/dylanirlbeck/tailwind-ppx/issues/34#issuecomment-619434321) [comments](https://github.com/dylanirlbeck/tailwind-ppx/issues/34#issuecomment-621479045) on my call for features, we should modify the PPX to instead look at the file where the Tailwind code is _included_ (i.e. wherever the user...
In order to truly convince people about the benefits of the PPX, we should do some sort of benchmarking with different project configurations and usage numbers of the PPX. I'd...
For example `bg-mono-800` and `bg-mono-300`.
- [x] Include suggestions i.e. `Did you mean 'flex-row'?`. We'll use the [Hamming distance](https://en.wikipedia.org/wiki/Hamming_distance) for this since there's a relatively small number of valid class names (we'll just extend the...