I've verified this issue to be present both when using xsd and RelangNG schemas.
Writing a docbook I write "<p" to start a new para node. I get a bunch of suggestions from the LSP and they are listed as expected in Vim as a float as I have coc-xml installed.
Most of the possible completions lack the angle brackets so when I choose "para" for example, then what I initially wrote as "<p" gets replaced by "para". I expect the result to be "".
I'm not sure if this is a bad config on my end but I lean towards it. Many others would complain about this if it really was a bug in the LSP. I cannot say which configuration it is though.
Can you give me some hints/ideas on what I can check?
I have no settings in my coc-settings.json for coc-xml. I've tried to uninstall coc-xml and install it again. The problem persist.
It might not even be an LSP issue as such. I tried installing https://www.npmjs.com/package/@xml-tools/language-server instead of coc-xml but using that produce the same issue as well.
Any hints and suggestions you can come up with is appreciated.
I've verified this issue to be present both when using xsd and RelangNG schemas.
Writing a docbook I write "<p" to start a new para node. I get a bunch of suggestions from the LSP and they are listed as expected in Vim as a float as I have coc-xml installed.
Most of the possible completions lack the angle brackets so when I choose "para" for example, then what I initially wrote as "<p" gets replaced by "para". I expect the result to be "".
I'm not sure if this is a bad config on my end but I lean towards it. Many others would complain about this if it really was a bug in the LSP. I cannot say which configuration it is though.
Can you give me some hints/ideas on what I can check?
I have no settings in my coc-settings.json for coc-xml. I've tried to uninstall coc-xml and install it again. The problem persist.
It might not even be an LSP issue as such. I tried installing https://www.npmjs.com/package/@xml-tools/language-server instead of coc-xml but using that produce the same issue as well.
Any hints and suggestions you can come up with is appreciated.