-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Intellij plugin v1.4 - The contents aren't fixed Crash #95
Comments
I'm also having this exact problem with Webstorm. It seems that the file is being formatted, but maybe it's the fallback IDE formatting. |
In my case I fixed the issue by removing biome.json working: {
// ...
"formatter": {
"enabled": true
},
"files": {
"include": [
"graphql/",
"src/"
]
}
} biome.json that stopped working: {
// ...
"formatter": {
"enabled": true,
"include": [
"graphql/",
// adding "src/" here also worked
]
},
"files": {
"include": [
"graphql/",
"src/"
]
}
}
I can't remember why I added |
I've barely touched my config since it was generated by biome from my eslint/prettier config. This is my current biome.json.
I have some "include" rules, but those are outside formatter |
This commit is causing issue (326675a#diff-1d281df78e3ab6c45cfa052c53e58bd1d824404f01fc9673c94104cecd0b9e96R101) looks like Just for curiosity, version 1.4 is available in JetBrains store, but there is no official release for 1.4 and last version here is 1.3, would be nice to make it right. Thanks for you work! |
FYI, I've been experiencing this issue on Webstorm |
same with me webstorm 2024.2.2 |
@sitole it's not the --write argument, I made a new plugin with the --apply argument then i get:
The fix was done because the --apply did generate warning and the plugin handles this as an error and "crashes". It would be nicer if the plugin first checks the version of biome and then use the correct arguments so the plugin keeps working for people who are using an older biome version. |
@bc-m I updated my local branch with your change and created a new plugin (that also logs the arguments), but I still get the error:
I asked in discord if somebody can explain what this error means since the proposed |
This issue is fixed with biome cli 1.9.3: biomejs/biome#4102 |
Thanks for the link @bc-m ! So think we can close this issue then, since it's a biome cli issue and not this plugin |
When pressing save it reports the following error:
Using biome 1.9
The text was updated successfully, but these errors were encountered: