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
Volar does not respect "Editor: Auto Closing Quotes" setting when writing attributes in templates #840
Comments
This is by new html config |
Ah, thanks, and sorry to bother you. |
Never mind, thanks for your report. :) |
Just out of curiosity, why does it only seem to affect my Vue templates and not pure HTML files or PHP or things like that? |
vscode do not release a new version with this feature yet. This feature does not rely on vscode client upgrades, so Volar can release this feature earlier than vscode. |
Ah, so it's an upcoming part of the spec, but the implementation is left up to extension maintainers rather than being built into VS Code itself? If the implementation is custom, do you have control over which quote gets overtyped? If I type |
HTML extension is built-in support by vscode, I just refer to the code of vscode to add it for vue.
I just follow the logic of vscode. You can open an issue in vscode. If vscode decides to change this logic, volar will change it together. |
Gotcha, thanks! |
@johnsoncodehk There seems to be a regression on Volar where it doesn't respect the |
When you start typing something like
class=
the Volar extension tries to be helpful and adds a pair of quotes automatically.I'm sure this is an intended feature. However, this disregards the setting in VS Code that allows the developer to disable "Editor: Auto Closing Quotes".
Personally, I find auto quotes or brackets distracting, as I don't expect characters to appear without my input, so I have that setting set to "never". I'm sure that I'm in the minority on that preference, given the fact that the setting is enabled by default, but I do think I'm justified in expecting an extension to respect this preference, or to add a setting of its own to disable auto quotes.
The text was updated successfully, but these errors were encountered: