CodeAction doesn't work in VSCode about vscode-xml HOT 5 CLOSED

This is weird. I don't see why it doesn't work, but my guess is the textedit is malformed (missing fields?)

from vscode-xml.

Perhaps it's a problem from lsp4xml which doesn't create the well range?

from vscode-xml.

It seems that vscode doesn't support edits for CodeAction and only command. The CSS Language Server had similar problem, see microsoft/vscode#57440 (comment)

from vscode-xml.

lsp4xml returns now list of Command instead of CodeAction (like CSS Language Server). It requires that this command must be registered on client side. See my PR at #34

from vscode-xml.

@fbricon I would like to provide codeaction for vscode-xml. It seems you are not OK with my #34 (which works like CSS Language Server).

Could you help me to configure vscode-xml to support codeaction literal please. Otherwise if it's not possible (vscode supports codeaction literal?) is it possible to accept my PR #34 and after we will change it as soon as vscode supports code action literal.

CSS Language Server supported CodeAction list but they change it to Command list (see microsoft/vscode#57440 (comment)), so I tell me if vscode does that, I think vscode doesn't support CodeAction literal?

Thanks for your help!

from vscode-xml.