Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: annotation support to highlight valid's className #1142

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

hyoban
Copy link

@hyoban hyoban commented Jan 26, 2025

ScreenShot 2025-01-26 16 48 20

This is very helpful for us to figure out whether the className is correct. I may not do well in some places, please point it out; I am happy to modify and improve it.

@thecrypticace
Copy link
Contributor

Hah, fun fact I actually had a "debug" version of this idea at one point to help me visualize individual classes vs class lists when using custom regexes while I was debugging some issues.

I really like this idea in general but I'll need to think on the implementation some as I think there are two main ways to approach this:

  • Use it to analyze what "spans" of text are being matched by custom class regexes
  • Use it to analyze what individual classes are being matched by Tailwind CSS itself / Oxide.

I think both of these approaches could use useful and could also be nice power-user features to have.

Also wanted to let you know it may be a bit before I get back to this PR but in general — very much like the idea. I have some ideas for changing how documents are handled in IntelliSense to simplify / unify the implementations of several features. I think this could be a good feature to add after that refactor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants