Create a XML with DTD subset which have error like this:
<!DOCTYPE root-element [
<!ELEMENT root-element (#PCDATA)>
XXXXXXX
]>
<root-element>
|
</root-element>
Open completion inside root-element, you should see 2 errors logs:
[Trace - 09:09:55] Received notification 'window/logMessage'.
Params: {
"type": 1,
"message": "May 30, 2020 09:09:55 org.eclipse.lemminx.extensions.dtd.contentmodel.CMDTDContentModelProvider createInternalCMDocument()\r\nMessage: Error while loading DOCTYPE subset\r\n::::3:3:41:The
...
[Error - 09:09:55] May 30, 2020 09:09:55 org.eclipse.lemminx.extensions.dtd.contentmodel.CMDTDContentModelProvider createInternalCMDocument()
Message: Error while loading DOCTYPE subset
::::3:3:41:The markup declarations contained or pointed to by the document type declaration must be well-formed.
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source)
...
Those 2 logs comes from of loading of CMDocument (to manage XML completion, hover based on DTD subset when subset declares <!ELEMENT). The load of CMDocument should never report errors.
Create a XML with DTD subset which have error like this:
Open completion inside root-element, you should see 2 errors logs:
Those 2 logs comes from of loading of CMDocument (to manage XML completion, hover based on DTD subset when subset declares <!ELEMENT). The load of CMDocument should never report errors.