-
Notifications
You must be signed in to change notification settings - Fork 79
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
Completion & hover based on XSD with elementFormDefault="unqualified" doesn't work #311
Comments
For your usecase you mena after templates you hav enone completion (like Site), I supsect it's a problem with namespaceURI computing.
Thanks! |
@angelozerr thanks! do you feel that there is a workaround I can implement? |
elementFormDefault="unqualified" See redhat-developer/vscode-xml#311 Signed-off-by: azerr <[email protected]>
@ynohat I fixed the problem in PR eclipse/lemminx#855 Please wait for merging this PR and after that you will able to install vsix and try it. |
elementFormDefault="unqualified" See redhat-developer/vscode-xml#311 Signed-off-by: azerr <[email protected]>
elementFormDefault="unqualified" See redhat-developer/vscode-xml#311 Signed-off-by: azerr <[email protected]>
elementFormDefault="unqualified" See redhat-developer/vscode-xml#311 Signed-off-by: azerr <[email protected]>
Fixed by eclipse/lemminx#855 |
Hi @angelozerr, thanks again for your quick response to this! Is this now in the following vsix? vscode-xml-0.14.0-10301.vsix | 26-Aug-2020 03:50 | 7.0M |
Just tested, and it seems to be working now 🥇 |
Great! Thanks for your feedback. |
Hi!
I am attaching an example XML file (examples/itops.xml) along with supporting schemata and a catalog (that I have setup in VS Code).
Autocomplete works on the fields under the root tag, but not children. Everything seems valid (but I'm no guru). Eclipse WTP (2020-06) autocompletes, using the same catalog and files.
rh-vscode.zip
Note that there are several schemata imported, and they use elementFormDefault="unqualified" (a UX choice, that could be revisited if proven anti-standard).
Thanks a lot for an amazing extension!
The text was updated successfully, but these errors were encountered: