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
I'm a frequent user of your VSCode extension, specifically the feature that provides IntelliSense for CSS class names in Typescript JSX. It's been incredibly helpful in my web development workflow.
I would like to suggest a feature enhancement that could further improve the utility of the extension. My proposal is to introduce an option that allows users to define custom regex patterns for identifying areas in the code where class name autocompletion should be activated.
This feature would be similar to the tailwindCSS.experimental.classRegex configuration (usage) available in the Tailwind CSS IntelliSense extension. Such a capability would enable users to have more control over where and how class name suggestions are presented, enhancing the extension's flexibility to accommodate different coding styles and frameworks.
To give you a better understanding of my use case: in my development environment, I work with a custom CSS class generator built on TailwindCSS. This generator is tailored to support features like interactive and dark modes, using classes such as .border-background { @apply border-[#FFFFFF] dark:border-[#000000]; }. Since my TailwindCSS configuration doesn't encompass any colors, I rely on your extension for CSS IntelliSense.
The addition of regex support would immensely improve my workflow by allowing the IntelliSense to more accurately predict and suggest class names based on my unique setup. It would also offer greater flexibility for developers working with custom frameworks or unconventional HTML structures.
I believe this feature would not only benefit me but also a wide range of developers who might be in similar situations.
Thank you for considering this enhancement. I am eager to contribute any further details that might be needed and am looking forward to the possibility of this feature's integration.
Best regards,
The text was updated successfully, but these errors were encountered:
I'm a frequent user of your VSCode extension, specifically the feature that provides IntelliSense for CSS class names in Typescript JSX. It's been incredibly helpful in my web development workflow.
I would like to suggest a feature enhancement that could further improve the utility of the extension. My proposal is to introduce an option that allows users to define custom regex patterns for identifying areas in the code where class name autocompletion should be activated.
This feature would be similar to the
tailwindCSS.experimental.classRegex
configuration (usage) available in the Tailwind CSS IntelliSense extension. Such a capability would enable users to have more control over where and how class name suggestions are presented, enhancing the extension's flexibility to accommodate different coding styles and frameworks.To give you a better understanding of my use case: in my development environment, I work with a custom CSS class generator built on TailwindCSS. This generator is tailored to support features like interactive and dark modes, using classes such as
.border-background { @apply border-[#FFFFFF] dark:border-[#000000]; }
. Since my TailwindCSS configuration doesn't encompass any colors, I rely on your extension for CSS IntelliSense.The addition of regex support would immensely improve my workflow by allowing the IntelliSense to more accurately predict and suggest class names based on my unique setup. It would also offer greater flexibility for developers working with custom frameworks or unconventional HTML structures.
I believe this feature would not only benefit me but also a wide range of developers who might be in similar situations.
Thank you for considering this enhancement. I am eager to contribute any further details that might be needed and am looking forward to the possibility of this feature's integration.
Best regards,
The text was updated successfully, but these errors were encountered: