Skip to content
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

Deleting or creating settings.json in .vscode does not trigger onDidChangeConfiguration notification #92288

Closed
Colengms opened this issue Mar 9, 2020 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues verified Verification succeeded
Milestone

Comments

@Colengms
Copy link
Contributor

Colengms commented Mar 9, 2020

This is based on this symptom in the C/C++ Extension: microsoft/vscode-cpptools#5023

This is regarding settings.json in the .vscode subdirectory within an open folder.

If settings.json is edited, either within or externally from VS Code, we appear to get onDidChangeConfiguration. However, if the file is deleted, or created (one copied into place), we do not get onDidChangeConfiguration.

Likely unrelated, but: I also see that we are getting duplicate file watcher events for files within the .vscode subdirectory. We don't see duplicates for files in other subdirectories. I've repro'ed on both Windows and Linux.

@roblourens roblourens assigned sandy081 and unassigned roblourens Mar 22, 2020
@sandy081 sandy081 added bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues labels Mar 27, 2020
@sandy081 sandy081 added this to the March 2020 milestone Mar 27, 2020
@roblourens roblourens added the verified Verification succeeded label Apr 3, 2020
@github-actions github-actions bot locked and limited conversation to collaborators May 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants