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
Additional context
I installed this plugin in tandem with roobert/tailwindcss-colorizer-cmp.nvim in order to see colors of tailwind classes in my code. When going through the options, I noticed that it had the same issue because the tailwind colors were hardcoded. Luckily js-everts created cmp-tailwind-colors, which is the same but gets the colors from tailwind directly instead of hardcoding a list of values. I can see in the tailwind.lua file of this plugin that you might be doing something similar for user defined colors, but I'm not sure. If possible, not using hardcoded colors seems like a good thing to get working. If not, just updating the colors with the new shade in tailwind v3.3 would be fine :-)
The text was updated successfully, but these errors were encountered:
Describe the bug
The new 950 shades included in tailwind v3.3 are not highlighted.
To Reproduce
Use a classname like
text-red-950
.Expected behavior
The text is colorized.
Screenshots
Operating System:
MacOS
Neovim Version:
NVIM v0.8.3
Build type: Release
LuaJIT 2.1.0-beta3
Colorizer Version:
dde3084
Additional context
I installed this plugin in tandem with roobert/tailwindcss-colorizer-cmp.nvim in order to see colors of tailwind classes in my code. When going through the options, I noticed that it had the same issue because the tailwind colors were hardcoded. Luckily js-everts created cmp-tailwind-colors, which is the same but gets the colors from tailwind directly instead of hardcoding a list of values. I can see in the
tailwind.lua
file of this plugin that you might be doing something similar for user defined colors, but I'm not sure. If possible, not using hardcoded colors seems like a good thing to get working. If not, just updating the colors with the new shade in tailwind v3.3 would be fine :-)The text was updated successfully, but these errors were encountered: