Linting makes editing hard

The screenshot shows a simple file which only misses the end tag </xs:schema>. This little issue results in the whole document being marked invalid, which doesn’t help much. The file becomes harder to read while editing and doesn’t tell much about the origin of the error.

I’d expect only the opening tag name and/or the end of the document being marked invalid. The content in between is very correct.

[angelozerr]

If old in “Keep the old diagnostic range on clients that don’t support.” means current behavior, I would say “yes”

[predragnikolic]

Does the Sublime LSP client support relatedInformation?

Yes, LSP for Sublime Text does support it.

Here is an example gif

Keep in mind that I hard coded the response to include the diagnostic.relatedInformation field, so this is actually not provided by the language server, but rather just for demonstrating purposes.

Sublime Text just shows related diagnostics information in the hover popup, when hovering over the diagnostics.

    diagnostic['relatedInformation'] = [{
            'location': {
                'uri': '/home/predrag/Documents/modulll/src/App.jsx',
                'range': {
                    'start': { 'line': 9, 'character': 15 },
                    'end' : { 'line': 9, 'character': 15 }
                },
            },
            'message': 'Missing closing tag here'
    }]

VS Code show relatedInformation in the diagnostics panel and the hover popup.