Does this debugging work for you and/or is there some additional obvious trick I am not aware of?
1) all lsp features on lsp vscode side is managed by the vscode-languageclient npm module. The spirit of lsp is to develop nothing on client side when you develop a language server. Lsp client impl like eclipse ide with lsp4e, vscode with bscode-languageclient follow the lsp spec and when you develop a language server it should work out of the box in any lsp client
In other words vscode-xml has not code for standard lsp features like completion, diagnostics,codelens, hover....
2) have you read https://github.com/redhat-developer/vscode-xml/blob/master/CONTRIBUTING.md#on-vscode ? The remote launch is used to debug lemminx inside vscode
XML extension does not work?
Say I have the following file
<?xml version="1.0" encoding="utf-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.openxmlformats.org/wordprocessingml/2006/main"
xmlns:s="http://schemas.openxmlformats.org/officeDocument/2006/sharedTypes"
elementFormDefault="qualified" attributeFormDefault="qualified" blockDefault="#all"
targetNamespace="http://schemas.openxmlformats.org/wordprocessingml/2006/main">
<xsd:import namespace="http://schemas.openxmlformats.org/officeDocument/2006/sharedTypes"
schemaLocation="shared-commonSimpleTypes.xsd"/>
<xsd:complexType name="CT_OnOff">
<xsd:attribute name="val" type="s:ST_OnOff"/>
</xsd:complexType>
</xsd:schema>The extension resolves s:ST_OnOff correctly but pressing F12 "Go to definition" on it doesn't work. Is it supposed to?
or apply syntax highlight for custom extensions?
and you select XML as language
you can use settings too https://code.visualstudio.com/docs/languages/overview#_adding-a-file-extension-to-a-language
Once your file will be considered as XML, you will enjoy with syntax coloration and compeltion, validation, etc if you install vscode-xml
10 spaces
when I delete it and afterwards install it again, it will not ask me for some settings like in the first time
e.g. the telemetry option
which settings are responsible for that?
Can you confirm I am doing it right by any chance?
oh interesting, looks like it did start working
In the settings.json I added this:
"xml.symbols.enabled": true,
"xml.symbols.maxItemsComputed": 30000,
"xml.symbols.filters": [
{
"pattern": "*.bpml",
"expressions" :[
{
// Process Name
"xpath": "//process/@name",
}
]
}
]
"xml.symbols.enabled": true,
"xml.symbols.maxItemsComputed": 30000,
"xml.symbols.filters": [
{
"pattern": "*.bpml",
"expressions" :[
{
// Process Name
"xpath": "//process/@name",
}
]
}
]
But my XML is still parsed out as:
process
rule
condition
rule
condition
process
rule
condition
rule
condition
I was expecting it to be something like
process
name=hello
rule
condition
rule
condition
process
name=hello
rule
condition
rule
condition
thank you
Do you happen to know what the first version of the plugin this was available in? I want to load it to see if it works in other versions before it might have broke
help:
Please create an issue at https://github.com/redhat-developer/vscode-xml/issues like I suggested in https://github.com/eclipse/lemminx/issues/1263#issuecomment-1196465142 by giving us some traces and explain in details where you have this problem (when you open a XMLfile, is it a big XML file, do you use binary mode,etc). It will easier to discuss about that in a vscode-xml issue.