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
initialize a tailwind project (i.e. create tailwind.config.js with some text)
write something like this, then wait for the LS to start completion:
<div class="text-[cursor]"></div>
3.1. if the completeion starts too early, write text-red then delete the red part
4. continue writing red
I expected this to happen:
it should suggest text-red-[number]
Instead, this happened:
it suggested divide-red-[number], which doesn't match what I have
Helix log
~/.cache/helix/helix.log
please provide a copy of `~/.cache/helix/helix.log` here if possible, you may need to redact some of the lines
2025-01-15T13:03:49.996 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
It could be related to #12501. @nik-rev What do you think?
what #12501 does is check if the documentation for each Color item ends with a valid hex code, and if so, use it to display a colored box. It doesn't affect the completion algorithm at all
Summary
tailwind LS gives invalid suggestions when the completion starts after first
-
Reproduction Steps
https://asciinema.org/a/8CCtaplo2JFn3z2ZfoJeZgluL
I have created a repro repo s.t. you don't have to.
https://github.com/aster-void/helix-repro/
I tried this:
tailwindcss-language-server
tailwind.config.js
with some text)3.1. if the completeion starts too early, write
text-red
then delete thered
part4. continue writing
red
I expected this to happen:
it should suggest
text-red-[number]
Instead, this happened:
it suggested
divide-red-[number]
, which doesn't match what I haveHelix log
~/.cache/helix/helix.log
Platform
Linux / NixOS
Terminal Emulator
kitty 0.38.1 created by Kovid Goyal
Installation Method
flake
Helix Version
helix 25.01 (ca19496)
The text was updated successfully, but these errors were encountered: