-
Notifications
You must be signed in to change notification settings - Fork 82
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
XML support crashes when workspace folders are empty #940
Comments
Could you enable trace with |
Thanks, here is the log, and the listed "getWorkspaceUri" was a hint to the solution: I had tried to use workspaces ( Maybe the title should become "is broken by workspace files"?
|
Thanks so much @Chadehoc for your feedback and trace. is it possible to share your vscode project which causes the problem please. |
Trying to reproduce a stripped-down example, it seems as simple as creating an empty
I can't check for sure that my original code-workspace file was indeed empty (it was deleted and rewritten since), but it is possible, because it had been a simple try out of curiosity. Anyway, it reproduces the activation error whatever the XML file. |
Fixes redhat-developer#940 Signed-off-by: azerr <[email protected]>
Fixes #940 Signed-off-by: azerr <[email protected]>
@Chadehoc my PR has been merged, tomorrow you should enjoy with vscode-xml prerelease https://github.com/redhat-developer/vscode-xml#contributing (checks the date before installing). Please give us feedback if it fixes your issue. |
I had used this extension with success some times ago (say, last month), including schema validation and formatting.
When I came back to it, editing the same XML files I did before, suddenly the only item offered by the command palette had become "XML: Open XML Documentation", and nothing works (validation, formatting, auto-closing tag when typing "/"...).
I have tried to reinstall the extension, remove every personnalized settings, install the RC version, disable all other extensions... in vain. (Note:
vscode-xml
was my latest installed extension.)The text was updated successfully, but these errors were encountered: