No support for language specific settings

[medikoo]

e.g. having in VS Code settings:

"[markdown]": {
  "prettier.tabWidth": 2
},

Is reported as Uknown editor configuration setting and indeed has no effect

[CiGit]

VSCode only allows some settings in language settings. mostly editor. ... like editor.formatOnSave

Extensions are unaware of those settings when using Settings API.(Without re-implementing the logic)

[medikoo]

@CiGit corresponding issue is here: microsoft/vscode#26707

Still, it's clear that extensions can support it, as it can be retrieved as:

workspace.getConfiguration().get('[markdown]')['prettier.tabWidth']

Are you trying to say that there's no plan to support that at this point

[CiGit]

Thanks for the link.

workspace.getConfiguration().get('[markdown]')['prettier.tabWidth']

This is what I meant by re-implementing

I'm pretty convinced this should be implemented by VSCode.
We may have to annotate our settings tho. We already do that to support multiple workspace (scope: "resource")

We already have a mean to scope settings by language, prettier config files support that.
https://prettier.io/docs/en/configuration.html#configuration-overrides

[CiGit]

Seems you use .editorconfig overrides should also work 😃

[medikoo]

Seems you use .editorconfig overrides should also work

Sure, but I just wanted to address the prettier specificity, that for no code snippets it uses spaces instead of tabs (and then I would like to have it kept at 2).

Now it seems wrong to put it in editorconfig, as it's general (not just for prettier), and I don't want to force tabsWidth setting when project is indented with tabs (tabsWidth should be up to developer liking).

We already have a mean to scope settings by language, prettier config files support that.

If I can have config at home directory that will affect any project, then indeed it can be solution (otherwise I don't want to pollute every single project repo with that).
I'll check it, thanks

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.