-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
🐛 Graphql files are ignored or not supported. #481
Comments
I can confirm that I am having the same issue. On 2 different Linux machines, Biome version 1.9.4, extension 2.3.0, and VS Code 1.96.4 |
Hey, thanks for opening this issue and providing the minimal reproduction. I was able to reproduce it. We did add GraphQL to 2.x in #252, but it looks like we forgot to publish a new 2.x minor including the changes 🫢. I plan to address it this week-end. In the meantime, you can switch to the pre-release channel, which does not suffer from the issue. |
Yep this is what we have been using since October, but in our large team we can't tell people to use the pre-release version and on vscode, there is no way to specify recommended extensions with a specific version. Btw the bug should stay open until the fix is shipped on production, to avoid more duplicates. |
Done. v2.3.1 fixes this. |
Lovely, thank you! |
You're welcome! |
VS Code version
1.96.4
Extension version
2.3.0
Biome version
1.9.4
Operating system
Description
Same as #378.
The referenced issue has been closed on 4 October 2024 (in a preview release?) but the bug still exist in production today 30 Jan 2025 since the fix is not shipped yet.
When opening
.graphql
files in vscode the extension is not running (CLI works as expected). Consecutelly, parsing, linting and formatting don't work. See the screenshot below. The server is running and biome works for other files.Steps to reproduce
.graphql
file and open itExpected behavior
As per the doc, the biome should be fully compatible with Graphql, and the CLI works as expected. So we think may be related to this official extension.
Does this issue occur when using the CLI directly?
No
Link to a minimal reproduction
https://github.com/lualtek/biome-repro-1738242624705
Logs
Expand full log
The text was updated successfully, but these errors were encountered: