Syntax highlighting can be brittle

[patrickhulce]

Steps to Reproduce

1. Create a snapshot file with the following content

exports[`file should handle HTML-like stuff 1`] = `"<input id=\\"label-text-input\\" type=\\"text\\">"`;

exports[`file should handle HTML-like stuff 2`] = `now everything is ugly for the rest of the file :(`;

Expected Behavior

Syntax highlighting is broken/off within the string, but not outside it

Actual Behavior

Syntax highlighting is broken for the entire file

---

It looks like the snapshot grammar is a fork of the TypeScript grammar, but the commit (e5d1aa0) doesn't seem to show what was changed. Perhaps just rolling to the latest TypeScript one might help?

[connectdotz]

seems easy enough, want to give it a try ? CONTRIBUTING

[alexilyaev]

Experiencing as well, the angled brackets are messing with the highlighting:

If snapshots are just valid TypeScript code, then why do we have a custom syntax highlighting file?

Adding this to User Settings works as expected:

  "files.associations": {
    "*.snap": "typescriptreact"
  },

[moltar]

Also Date objects:

[mikestopcontinues]

Here's another example, with two cases on lines 63 and 94...