Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Svante
    @svanteschubert
    2) I was able to debug lemminx by attaching to "Launch Extension" but I have trouble to get extension running (no output of LSP protocol) when trying to attach via "Launch Extension and wait for remote debugger". I am using atm IntelliJ IDEA on Linux.
    Does this debugging work for you and/or is there some additional obvious trick I am not aware of?
    Angelo
    @angelozerr
    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
    joe914
    @joe914
    xmlExtension.png
    XML extension does not work?
    joe914
    @joe914
    it is ok after uninstalling other XML extensions and reinstalling this extension
    Angelo
    @angelozerr
    You mean that its working now? If it that which extensions do you have installed?
    Ben Toner
    @bentoner

    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?

    Angelo
    @angelozerr
    Perhaps its a usecase we have not covered. Please create an issue in lemminx github repository by adding your sample in the issue.
    Danila Fomin
    @Dancheg97
    Hello! Is that possible to apply syntax highlight or formatting for .config files in dotnet project in vscode?
    image.png
    or apply syntax highlight for custom extensions?
    and you select XML as language
    Once your file will be considered as XML, you will enjoy with syntax coloration and compeltion, validation, etc if you install vscode-xml
    Danila Fomin
    @Dancheg97
    thx a lot, that helped!
    Angelo
    @angelozerr
    you are welcome
    derived-coder
    @derived-coder
    Hi, I have enable "xml.format.splitAttributes": true, however, it looks like he is suing a lot of spaces to indent the attributes
    10 spaces
    Angelo
    @angelozerr
    Please create an issue in vscode-xml with detailed information
    derived-coder
    @derived-coder
    how can I completely remove the extension with all its settings?
    Angelo
    @angelozerr
    sorry I don't udnerstand?
    derived-coder
    @derived-coder
    How can I delete the extension?
    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
    derived-coder
    @derived-coder
    how do I control the spaces of attributes indention?
    which settings are responsible for that?
    Angelo
    @angelozerr
    Unisntall vscode xml doesnt remove your settings
    Nick Blyumberg
    @nblyumberg_twitter
    Hello, I am trying to update the outline to show attribute names for some xpath. I edit the setetings.json and include my xpath but I never see the outline updated
    Angelo
    @angelozerr
    You need to update your xml file to refresh the outline after settings.json changed. If it doesnt work please create an issue to vscode-xml with detailled information
    Nick Blyumberg
    @nblyumberg_twitter
    I close and reopen the XML file
    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",
    }
    ]
    }
    ]
    But my XML is still parsed out as:
    process
    rule
    condition
    rule
    condition
    I was expecting it to be something like
    process
    name=hello
    rule
    condition
    rule
    condition
    Nick Blyumberg
    @nblyumberg_twitter
    Even trying "xpath": "//@name" doesn't seem to work
    Angelo
    @angelozerr
    please create an issue and share your XML + settings.json
    Nick Blyumberg
    @nblyumberg_twitter
    ok
    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
    Angelo
    @angelozerr
    I don't remember that (I could find it) but could you try to use filter with file extension .xml instead of .bpml ?
    Nick Blyumberg
    @nblyumberg_twitter
    I did try it with .xml with same results
    lautnerxing
    @lautnerxing
    image.png
    help:
    Angelo
    @angelozerr
    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.