-
Notifications
You must be signed in to change notification settings - Fork 125
"quote_type" didn't added to editorconfig file. #303
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
Comments
The There is no general quote style option in VSCode. Therefore, if the requested functionality is implemented, the extension should account for different languages. For example, if # there should be a key-value collection of settings groups and related file extension
# like { "javascript.preferences": ["js", "mjs"] }
[*.{js,mjs}]
quote_type = single All options are provided by extensions (either built-in or external) and must be manually checked. All of this will become a mess in the blink of an eye. Respecting formatter-specific preferences isn't realistically possible, as there are many formatters, each supporting different languages and having different settings that affect how and to which files options are applied. @xuhdev request your opinion |
@xuhdev you responded to two mentions yesterday, so tagging you again |
@SunsetTechuila Sorry I missed your message earlier.
Editor plugins can support custom properties, and I don't believe we have a strict definition of "official" plugins here -- so far most editor plugin developers enjoy a high degree of freedom. However, we don't have a uniform opinion on the naming of such custom properties yet, see editorconfig/editorconfig#332 . However, likely we should add some unique prefix at the very least, such as
I don't understand VSCode that much and will always leave VSCode specific decisions to you 😉 |
Not included in the spec but see editorconfig/editorconfig#410 which points to https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties#ideas-for-domain-specific-properties where quote_type is the first nonstandard property on the list. It might also be worth considering what other tooling looks at this value -- several commenters have brought up support in |
Uh oh!
There was an error while loading. Please reload this page.
Please fill-in this template.
code --disable-extensions
and the issue did NOT present itself.Delete the following condition if it doesn't apply to your case:
If the extension is not picking up the expected configuration for a file:
npm install editorconfig -g
and raneditorconfig [file-in-question]
and the configuration was what I expected. If not, please file on theeditorconfig-core-js
issue tracker.Issue
1.55.0
0.16.4
Root
.editorconfig
FileAre there any other relevant
.editorconfig
files in your project? Nojavascript.preferences.quoteStyle
auto
single
typescript.preferences.quoteStyle
auto
single
prettier.singleQuote
false
true
prettier.jsxSingleQuote
"false"
"true"
File opened
./test.js
Expected behavior
Actual behavior
Additional comments or steps to reproduce
.
The text was updated successfully, but these errors were encountered: