How does this compare to `redhat-developer/vscode-xml`?

[RokeJulianLockhart]

Why this would be preferable isn't immediately obvious, not having utilised either. I ask about that project specifically because it's the most popular VS Code XML formatter, with solely this in second place by a long shot.

[tina838]

``

[RokeJulianLockhart]

#399 (comment)

@tina838, what does that mean?

[datenimperator]

Probably late to the game, but since I stumbled across this because I found it on Google, I'd like to add my $0.02

Redhat's vscode-xml features powerful intellisense and completion. It validates DTD and XSD, and offers some refactoring. It does not do linting, though. In fact, it doesn't even support XQuery syntax.

This extension has less features with regard to refactoring, but does offer linting and XQuery. However it does so based on xqlint 0.4.1, which is seven years old and doesn't support eg the map syntax of XQuery 3.1. There's an ancient discussion about integrating it, see wcandillon/xqlint#77

Since we are using XQuery 3.1 syntax here, I'm trying to decide whether I should accept the shortcomings of an old parser or skip the linting altogether. And in that case, I'd probably switch to the Redhat vscode-xml extension.