On a more general note, I think that is not very smart to scan for classes in source code, especially since elixir has metaprogramming. In theory it would be possible to scan for dynamic classes throughout the phoenix compiled templates and detect specifically a couple of things:
- Compute dynamic strings that can be resolved at compile-time (macros);
- Deliver warnings to user (this can be done by a separate system, however it would be nice if integrated);
- Have less content to scan (handling only compiled templates to tailwind, it doesn’t need to scan entire codebase blindly).
@zachdaniel it would be great to know what your opinion is and what the Tails library was aimed to solve, and if it can be used to create some of these features.
. I do see that it kind of defeats the real goal of helping people avoid the footgun. A custom compiler could work. It would be…pretty difficult though. Likely filled with false negatives or false positives depending on the implementation.
but PRs welcome if someone wants it. I did manage to add a sigil that should clean things up.
