Hi all, it’s been a while since the last time, but there’s a new release for elm-review!
This one allows rule authors access arbitrary non-Elm files, which enables a lot of new rule possibilities. I hope you enjoy it!
15 Likes
Very cool!
The css feature reminds me of the following rules/postcss plugin I wrote recently, but it’s TailwindCSS only. I think that case specifically does not really get improved by the new features, since it needs to analyze files generated by tailwindcss so there is a code generation step involved regardless.
I wonder if I can validate matching port implementations or matching webcomponent properties/attributes using elm-review now. Probably yes if both sides follow certain conventions.
https://package.elm-lang.org/packages/anmolitor/elm-review-tailwindcss/latest/
1 Like
This sounds like a fantastic project idea! @brian I feel like you might be interested in something like this.
@andreasmolitor Those are some really nice rules 
I think that if Tailwind’s configuration was easier to analyze, you could probably skip the generation, but I think that’s a bit out of reach (and possibly hard to maintain with changes from the Tailwind authors), looking at the generated CSS could be a reasonable middle-ground.
I wonder if I can validate matching port implementations or matching webcomponent properties/attributes using elm-review now. Probably yes if both sides follow certain conventions.
I think it’s worth trying!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.