-
-
Notifications
You must be signed in to change notification settings - Fork 433
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
Running 'Vue - Official' Formatter (configure) #5287
Comments
看起来这很可能是很多人碰到的保存卡顿问题,但在这之前一直没有人发 issue,所以我们对这个问题无从下手。不过我还没有找到稳定复现的方法,你方便的话可以来远程调试吗? https://github.com/vuejs/language-tools/wiki/Help-Us-Investigate-Issues-Remotely |
这个问题今天依然出现。昨天还没有卡顿检测。 |
有可能和网络有关 |
@subdavis Thanks for the reply, but I don't have the sibiraj-s.vscode-scss-formatter plugin installed locally. |
Vue - Official extension or vue-tsc version
2.2.8
VSCode version
Version: 1.98.2 (Universal) Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78 Date: 2025-03-12T13:32:45.399Z Electron: 34.2.0 ElectronBuildId: 11161602 Chromium: 132.0.6834.196 Node.js: 20.18.2 V8: 13.2.152.36-electron.0 OS: Darwin x64 24.3.0
Vue version
3.5.13
TypeScript version
5.8.0
System Info
package.json dependencies
Steps to reproduce
当保存文件的时候会被格式化阻止保存文件,需要等1分钟然后右下角会弹出formatter对话框点击skip才会保存,如果不点skip则一直不会保存文件。非常影响开发速度。
When saving a file, it will be formatted to prevent the file from being saved, you need to wait for 1 minute, and then the formatter dialog box will pop up in the lower right corner, click skip to save, if you don't click skip, the file will not be saved. Very much influencing development.
What is expected?
修复格式化速度或加一个跳过保存格式化代码的功能。目前我没有勾中保存格式化文件,但依然进行了格式化。
Fix formatting speed or add a feature to skip saving formatting code. At the moment I didn't check the box to save the formatted file, but I still formatted it.
What is actually happening?
cmd+s保存/使用vim插件 :w/cmd+p -> save all file/也是一样的出现问题。
cmd+s save/use the vim plugin :w/cmd+p -> save all file/ is the same problem.
Link to minimal reproduction
No response
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: