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

[#681] re-enable file watcher #688

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

WB2210
Copy link

@WB2210 WB2210 commented Sep 21, 2024

#681

Re-enable the functionality of file watcher since clangd's builtin restart functionality does not refresh opened files in vscode, leading to potentially misleading ifdef view

package.json Outdated
@@ -144,7 +144,7 @@
"clangd.onConfigChanged": {
"type": "string",
"default": "prompt",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if to put prompt or ignore as default behavior

@@ -21,9 +21,7 @@ class ConfigFileWatcherFeature implements vscodelc.StaticFeature {

initialize(capabilities: vscodelc.ServerCapabilities,
_documentSelector: vscodelc.DocumentSelector|undefined) {
if ((capabilities as ClangdClientCapabilities)
.compilationDatabase?.automaticReload)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like us to keep respecting the server's automaticReload capability by default.

I was thinking of adding a new config option, like clangd.onConfigChanged.forceEnable: true, and only skipping this automaticReload check if that option is enabled.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added "onConfigChangedForceEnable" option

(I tried "onConfigChanged.forceEnable" instead of "onConfigChangedForceEnable" but
config.get("onConfigChanged.forceEnable") fails, it doesnt seem to work when fields have "." in it
Any idea?)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

onConfigChanged.forceEnable works fine for me during local testing, and the documentation of the relevant vscode API says that it supports dotted names.

Could you try again, and if it doesn't work for you then post the version you're trying for further investigation?

@@ -21,9 +21,7 @@ class ConfigFileWatcherFeature implements vscodelc.StaticFeature {

initialize(capabilities: vscodelc.ServerCapabilities,
_documentSelector: vscodelc.DocumentSelector|undefined) {
if ((capabilities as ClangdClientCapabilities)
.compilationDatabase?.automaticReload)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

onConfigChanged.forceEnable works fine for me during local testing, and the documentation of the relevant vscode API says that it supports dotted names.

Could you try again, and if it doesn't work for you then post the version you're trying for further investigation?

"clangd.onConfigChangedForceEnable": {
"type": "boolean",
"default": false,
"description": "Force enable of \"On Config Changed\" option regardless of clangd version."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also amend the description of onConfigChanged to read:

What to do when clangd configuration files are changed. Ignored for clangd 12+, which can reload such files itself; however, this can be overridden with clangd.onConfigChanged.forceEnable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants