You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fails to resolve config variables containing colons #2165
I have some configuration variables that share the same prefix and use '.' as a delimiter. This looks to be standard practice for vscode settings. e.g.
ml.sdk
ml.username
ml.foobar
I'm trying to include some sdk-relative include paths for IntelliSense like this in the workspace folder's settings.json:
"ml.sdk": "/path/to/sdk",
"C_Cpp.default.includePath": [
"${workspaceFolder}/**",
"${config:ml.sdk}/foo",
"${config:ml.sdk}/bar",
],
IntelliSense is unable to locate any of the headers in /path/to/sdk/foo or /path/to/sdk/bar.
If I change the '.' to '_' instead, e.g. ml_sdk, IntelliSense is able to locate the headers.
I have an extension that reads and writes these settings, e.g.
vscode.workspace.getConfiguration('ml').get('sdk');
so I'm not sure I can do that without having a '.' as a settings section-identifier.
Thanks for reporting this. Yeah, our typescript is throwing an exception in this case. We'll see if we can release this in our pending update -- if not, it'll go in the next update. See #2166 . This code has been around since February, so maybe VS Code changed how its APIs behave?
Activity
sean-mcmanus commentedon Jun 21, 2018
Thanks for reporting this. Yeah, our typescript is throwing an exception in this case. We'll see if we can release this in our pending update -- if not, it'll go in the next update. See #2166 . This code has been around since February, so maybe VS Code changed how its APIs behave?
Fix ${config:a.b} #2165 .
wpaul-magicleap commentedon Jun 21, 2018
Wow, thanks for the quick fix!
Fix ${config:a.b} https://github.com/Microsoft/vscode-cpptools/issues… (
sean-mcmanus commentedon Jun 22, 2018
Fixed with 0.17.5.