You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the suggestion. However, this would be hard to implement. To get all possible tailwindcss class names, the plugin would need to read the tailwind config, as it allows adding additional classes to tailwind.
Currently, the plugin is a simple textmate grammar that provides syntax highlighting using regular expressions.
With tailwindcss 4, the configuration system will change significantly, making it even more complex. Configurations can be split across multiple css files in different locations.
Given these upcoming changes, I think it makes sense to wait for tailwindcss 4 before starting an implementation attempt.
see these cases, only a few are tailwind. the syntax coloring should tell the difference.
The text was updated successfully, but these errors were encountered: