FIXED: Unable to resolve cmake-tools-schema:/schemas...

[aremmell]

I have reproduced this, and through sheer stubbornness, finally figured it out.

You're passing the location for the schema JSON files to vscode.Url.file, which VS Code internally translates as a path on disk. And it's the wrong path.

Unfortunately, sometimes a path like, folder/and/another1 doesn't always mean "relative to my current working directory–but ./folder/and/another1 does.

I found the rogue path construction code in dist/main.js (around line 50080), and as you can see by the attached screenshot, all I've done is add ./ in front of the paths, and everything's working fine now.

You do also need to empty `CMakePresets.json, and then invoke the "Delete Cache" / "Reset Extension State" actions from the command palette. Then quit VS code, restart it, and it should be gtg.

I am not 100% sure this applies to locales that exist and have a separate path constructed, so you'll want to check that too.

Please re-open and fix this one! It's difficult to navigate the JSON without a schema to help you along.

Thanks for listening, and thanks for the cool extension.

[gcampbell-msft]

@aremmell I agree that this is not ideal, marking this as a bug and we will add it to our backlog! Thanks for posting the issue.

[xisui-MSFT]

@gcampbell-msft This is affecting us too. Looks like can be fixed easily though, can you help?

[bobbrow]

I am prepping a PR for it. Duplicate of #2587. Thank you for locating the problem @aremmell!