The Language Server Protocol provides a feature known as Document Symbols/Outline. After this change, we noticed a 2-3x speed improvement on large files! In this case, the regex checked for attribute names, but as you can imagine multiple attribute name regex calls during parsing could become a bit taxing. To get a bit more technical, one improvement to speed was replacing the use of some regular expressions (regex) with hand-crafted java code. This release had a focus on performance improvements, and we did just that by both decreasing memory usage and improving server speed. With this release, the following documentation will now be properly displayed in Markdown, resulting in:Īdditionally, at the bottom of the description hyperlinks to the connected XSD file are provided:
XML allows for the use of Markdown or HTML, and when rendering HTML it did not display well with the LSP: In an XSD element, documentation can be written to provide some information on that element. Before you would have to figure out which element is being referenced in the XSD and then find the type definition of that element definition.ĭocumentation improvements Documentation from hover and completion is provided as Markdown: Similar to the previous ability to go to the type definition from an XSD file, you can also right-click and select Go to Type Definition to find the type that the XML implementation references. Jump to the definition of a type from the XML document: This will bring up the same pop-up window from Find All References as well as show how many there are. Similar to the Find All References, we also provide a CodeLens that is also clickable. See the number of references of a type as a CodeLens:
#Xml validator notepad++ download code#
Doing so in VS Code will open up a mid-sized window that groups together all references to that type, making it easy to find and read through every use of the type. You can now Ctrl+click and go directly to the definition without having to manually search for the definition through all the other implementations.īy selecting Find All References, you can now find all uses of the schema type. If you are in an XSD working with an element that uses a type, you might want to go to the actual definition of it to be able to see its structure. This auto-complete feature now gathers all existing types and provides them through completion. Normally, you would have to know which types have already been defined and then type it making sure to write it correctly. With the ability to highlight all references, users can scroll through the document and see all of these references without having to manually search for each use.Īfter defining a type, you can start applying it to elements in the XSD file. This type can be reused and applied to multiple areas in the document, which can lead to type occurrences being used all over the place. In XSD files, you can reference a type, a type defines a specific XML structure that the XML document must follow. Highlight a specific type in an XSD file: The image below shows a validation error on an XML file in VS Code after the XSD it is linked to was changed externally in vim. As of this release, the server will track that XSD file externally, detect all changes, and perform the appropriate actions. Originally for XML validation relative to the XSD, validation would only be triggered on an XSD change if it was open/changed internally within the VS Code application. XML file validation on external XSD changes: See below where a sequence with 2 elements is declared but only the first one is provided for completion: In version 0.8.0, we now provide only valid elements. Depending on many constraints such as minOccurs/maxOccurs, if the elements were in a sequence … the provided completion item could be invalid. Prior to this release when creating an element in either an XML or XSD document the auto-completion suggestions based on XSDs were not always correct. XSD-related updates Accurate XSD-based completion: You can now easily complete the confusing CDATA block, along with comments. Now tags are treated as hyperlinks and, through Ctrl+click, you can now jump around from either the start or end tag to the opposite end. Sometimes in large documents, the opposite start/end tag can be located off the screen somewhere else, making it difficult to find. This new release brings new features to provide even more support for XSD-related features (the blueprint file of an XML document) along with various performance improvements. A new and improved version of the Visual Studio Code XML Extension by Red Hat has been released under version 0.8.0.
0 kommentar(er)
