-
-
Notifications
You must be signed in to change notification settings - Fork 376
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 lsp doesn't seem to handle jsx #2221
Comments
What's the filename extension of this file? |
|
I cannot reproduce it but we have a similar report here #2085 (comment) Is this problem reproducible in a stable way? Can anyone share a repo? cc @cdvillard |
I'm using helix helix 23.10 (26b3dc29) on fedora 39 |
This doesn't look to me as an editor-specific issue because it is apparently VSCode in #2085 (comment). Folder structures of the project can be involved in these types of issues. So a reproduction shared as a repo is helpful. |
Here is the whole lsp communication in case that helps hx -> biome
biome -> hx
|
In hx -> biome, the param |
Yeah, it seems helix is sending incorrect information. We use language id as source of truth because it covers cases where users are writing files that aren't saved on the file system yet. |
Its an issue in my helix on configuration, thanks for your time |
Environment information
What happened?
the lsp shows this error,
Expected a type but instead found '>'.(parse)
the cli shows no errors
Expected result
no error
Code of Conduct
The text was updated successfully, but these errors were encountered: