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

Bug: tailwind colors do not include new 950 shades #59

Open
LeviOP opened this issue Apr 28, 2023 · 0 comments
Open

Bug: tailwind colors do not include new 950 shades #59

LeviOP opened this issue Apr 28, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@LeviOP
Copy link

LeviOP commented Apr 28, 2023

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
image

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 :-)

@LeviOP LeviOP added the bug Something isn't working label Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants