feat(vscode): move to usage of SnippetString new in vscode 1.8.0

[eriklieben]

No description provided.

[bigopon]

May I know how I'm supposed to use this feature please ? I have no ideas what it's useful for.

[eriklieben]

hmm, I might have wrongly tagged this after thinking about it. First wanted to go with re-factor, but that didn't feel good because logic is changing (this version only works in vscode 1.8.0 and up). Sorry for the confusion.

Visual Studio Code is deprecating the old way in which we could provide auto-complete because they now support the more generic TextMate snippets syntax (https://manual.macromates.com/en/snippets).
For the full discussion, see this: microsoft/vscode#3210

This pull request is a quick move over to that implementation of providing snippets, so that autocomplete doesn't stop working when the vscode team remove the now depreciated logic.
So from the user's point of view, not much is changing, the auto-complete should still work the same.

I am working on a new implementation to improve the auto-complete once and for all (which includes the snippet string logic), so that is better extensible, but that is not completed yet.

Then I am also able to easily add the logic you proposed in #18. And add back in support to get completions on the dot, like it used to work in vscode before 1.6.0. So for example, by default you would get value.bind="" as autocomplete option (less overhead by default), if you move to the dot, you get the extra options (one-way, two-way, one-time). Or you could just add an extra dot behind a normal attribute, like value. to get the binding options.

Once this is done I can update the screenshots/ videos of how things work and then we are back on stable grounds.

[bigopon]

Sounds great. Tks for your hard work 😄