fix for auto completion with escape sequence chars

[msivasubramaniaan]

What does this PR do?

This PR suggest characters with escape chars if needed

What issues does this PR fix or reference?

redhat-developer/vscode-yaml#1097

Is it tested? How?

Yes added test case for the fix

[coveralls]

coverage: 84.075% (-0.06%) from 84.136%
when pulling d3cf06d on msivasubramaniaan:fix-unescaped-char-at-completion
into 11eff5f on redhat-developer:main.

[coveralls]

coverage: 84.075% (-0.06%) from 84.136%
when pulling d3cf06d on msivasubramaniaan:fix-unescaped-char-at-completion
into 11eff5f on redhat-developer:main.

[coveralls]

coverage: 84.075% (-0.06%) from 84.136%
when pulling d3cf06d on msivasubramaniaan:fix-unescaped-char-at-completion
into 11eff5f on redhat-developer:main.

[datho7561]

This doesn't fix issue for me. Make the following document, and open completion at the |:

# yaml-language-server: $schema=https://raw.githubusercontent.com/RedCMD/TmLanguage-Syntax-Highlighter/main/vscode.tmLanguage.schema.json
|

Accept the completion "New Grammar".

The generated content is still broken.

[msivasubramaniaan]

@datho7561 The autocomplete on parent level not be possible with escape chars. We have workaround only at the level of each key. Please try on the level of begin and end

[datho7561]

The bug report was about the completing the content using the "New Grammar" completion. In order to address the bug, the "New Grammar" completion should work as expected, with the quotes properly escaped when necessary.

[msivasubramaniaan]

Yes but we can do the workaround only. Complete fix not be possible. I've tried it out fully.

[datho7561]

Okay. We should keep the original issue open since this doesn't fix it, but I agree that this is worth merging because it addresses the issue you wrote a test case for.

[datho7561]

Thank you Muthu, sorry for stalling the merge.