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

Incorrect order of suggestions in Tailwind LSP #16776

Open
1 task done
esko opened this issue Aug 23, 2024 · 1 comment
Open
1 task done

Incorrect order of suggestions in Tailwind LSP #16776

esko opened this issue Aug 23, 2024 · 1 comment
Labels
autocompletions Feedback for code completions in the editor defect [core label] popovers Feedback for tooltips, syntax hints, info popups, toasts, etc tailwind css Tailwind CSS styling framework support

Comments

@esko
Copy link

esko commented Aug 23, 2024

Check for existing issues

  • Completed

Describe the bug / provide steps to reproduce it

Order of suggestions in Zed's implementation of Tailwind LSP differs from VSCode and nvim LSP ones. This is especially distracting when using the common px- and py- padding classes, where Zed first suggests the rarely needed scroll-px- and scroll-py classes.

I'm not sure what the exact correct suggestions should be, but in this case the px- should be shown first. In VsCode if you type px-4, it lists first the px- classes and scroll-px- after that. In nvim (nvim-cmp) it only lists the px- classes. Of other editors Nova works similarly to VSCode.

Environment

Zed: v0.149.0 (Zed Preview)
OS: macOS 14.5.0
Memory: 36 GiB
Architecture: aarch64

If applicable, add mockups / screenshots to help explain present your vision of the feature

Zed:
Screenshot 2024-08-23 at 22 02 57

nvim:
Screenshot 2024-08-23 at 22 17 00

VSCode:
Screenshot 2024-08-23 at 22 10 05

If applicable, attach your Zed.log file to this issue.

No response

@esko esko added admin read Pending admin review defect [core label] triage Maintainer needs to classify the issue labels Aug 23, 2024
@lougreenwood
Copy link

I recently enabled tailwind and also noticed that the suggestions seemed messed up.

@JosephTLyons JosephTLyons added popovers Feedback for tooltips, syntax hints, info popups, toasts, etc tailwind css Tailwind CSS styling framework support autocompletions Feedback for code completions in the editor and removed triage Maintainer needs to classify the issue admin read Pending admin review labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autocompletions Feedback for code completions in the editor defect [core label] popovers Feedback for tooltips, syntax hints, info popups, toasts, etc tailwind css Tailwind CSS styling framework support
Projects
None yet
Development

No branches or pull requests

3 participants