Use textEdit instead of insertText; bad autocompletion for special characters

[mathaym25]

[SPGoding]

This issue has become critical as it blocks the process of merging JSON support logic in (#342).

VS Code requires all CompletionItems for JSON files contain a range property, whose type is Range | { inserting: Range, replacing: Range }.

The Language Server Protocol still hasn't any support for it, so we need to use the existing textEdit property instead. However it's desirable to support the new range logic since textEdit has been deprecated in VS Code, so instead of building LSP's CompletionItems directly, using an inner type would be preferable:

interface ParserSuggestion extends CompletionItem {
    /**
     * The start offset of the CompletionItem.
     */
    start: number,
    /**
     * The end offset of the CompletionItem in replacing cases.
     */
    replaceEnd: number,
    /**
     * The end offset of the CompletionItem in inserting cases.
     */
    insertEnd: number
}

This refactor requires a huge rewrite in almost every parser and their corresponding tests, hope I can survive it :D

[SPGoding]

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀