Skip to content

[VSCode] Option to choose where 'toggle inlay hints' setting is saved #6316

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

Closed
oeed opened this issue Oct 21, 2020 · 4 comments
Closed

[VSCode] Option to choose where 'toggle inlay hints' setting is saved #6316

oeed opened this issue Oct 21, 2020 · 4 comments
Labels
A-config configuration A-vscode vscode plugin issues S-actionable Someone could pick this issue up and work on it right now

Comments

@oeed
Copy link
Contributor

oeed commented Oct 21, 2020

I'm using the 'toggle inlay hints' command from #4601 and love it. The only issue is it saves the setting to the workspace, which I have included in my Git repo, so every time I toggle Git sees a change. It is committed as it's intended to hold the shared settings and folders for the team for each specific target in the monorepo; so having personal settings in there isn't ideal.

I can see it's currently hard coded here. I'd be quite happy to make a simple PR to add this option if open to the idea.

@SomeoneToIgnore
Copy link
Contributor

SomeoneToIgnore commented Oct 22, 2020

I see that this is the only place we pass any value into this parameter, all other cases make it undefined yet don't interfere with you workflow, do they?

Current docs for the parameter are:

* @param configurationTarget The [configuration target](#ConfigurationTarget) or a boolean value.
*    - If `true` updates [Global settings](#ConfigurationTarget.Global).
*    - If `false` updates [Workspace settings](#ConfigurationTarget.Workspace).
*    - If `undefined` or `null` updates to [Workspace folder settings](#ConfigurationTarget.WorkspaceFolder) if configuration is resource specific,
*     otherwise to [Workspace settings](#ConfigurationTarget.Workspace).

so I wonder if we really need any configuration at all, maybe we can simply remove it.

Anyway, the MR is welcome, thank you.

@oeed
Copy link
Contributor Author

oeed commented Oct 22, 2020

Oh interesting, do you know what is meant by "if configuration is resource specific"? Perhaps language specific? Although undefined/null only choses between workspace folder or workspace, not global.

I'll experiment with removing it, if that doesn't help I'll make a config for it and PR. Thanks

@lnicola
Copy link
Member

lnicola commented Dec 21, 2020

@oed did you try that?

@lnicola lnicola added S-actionable Someone could pick this issue up and work on it right now A-vscode vscode plugin issues labels Dec 21, 2020
@Veykril Veykril added the A-config configuration label Dec 17, 2021
@lnicola
Copy link
Member

lnicola commented Sep 19, 2022

The command was removed in #13215.

@lnicola lnicola closed this as not planned Won't fix, can't repro, duplicate, stale Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-config configuration A-vscode vscode plugin issues S-actionable Someone could pick this issue up and work on it right now
Projects
None yet
Development

No branches or pull requests

4 participants