Hey@deathaxe@rchl thank you for taking care of this!

I'd like to add some tests for the ST4 branch, I'd started on some early tests for#210 but do you think there are any tests we can add?

Let me know if you think this looks good, I can go ahead and make a release where ST4 gets the new branch.

I'll test this out myself. To be honest - I haven't had time to look at this in detail - but I'll definitely spend some time on this today.

What I can provide is in-the-field testing since I work with Vue files daily. Have been running with this change since yesterday and haven't noticed any issues.

@skyronic isn't there some blocking issue that makes some testing impossible?

@deathaxe can you provide a small example showing the superiority of this change vs.#214? I would just like to know what it fixes specifically that the other one didn't and test more stuff around that.

Added some tests and a Github Action to run them automatically. They should become active once, this PR is merged.

I took the config fromhttps://github.com/SublimeText-Markdown/MarkdownEditing/blob/3.0.0/.github/workflows/ci-syntax-tests.yml

Already found various other improvements, but I'll hold them off until this one is merged.

This is some absolutely stellar stuff,@deathaxe. Thank you!!

I tested it locally and it works great! Let me know when you're happy with it, and I'll merge and release.

@skyronic isn't there some blocking issue that makes some testing impossible?

@rchl - yes, there was indeed an issue I encountered while testing it. Something like

<style lang="sass">@import '~foo'// ^ source.sassa  color: red</style>

Would not work, because even though the// would be recognized as a comment, Syntax Tests needed to be wrapped inside a<!-- -->

I'm still not 100% sure how@deathaxe's tests work but it appears to be using HTML comment start/end punctuation in<script> and<style> tags. I would need to take a closer look.

Would not work, because even though the // would be recognized as a comment, Syntax Tests needed to be wrapped inside a<!-- -->

The comment character used for syntax tests is defined by the first line of the test file. Your test branch uses those html comments in the first line, which would mean to wrap all test cases in such. That's more than cumbersome. Hence core HTML.sublime-syntax uses##. I've just choosen// because it seems more common.

I found some bug in template tag handling, I am not sure about the waymustache-expression is implemented and would suggest to reorganize the syntax a bit to group contexts which belong together and sort those groups to match the order of core HTML.sublime-syntax.

All of that could happen soon, but feels out of scope for this PR.

I'd open new ones for the mentioned fixes.

I've removed Github Actions for now as it appears to be more work than expected.

It probably fails due to missing embedded syntax packages. Investigating and fixing it is really out of scope here.

This PR contains all fixes required to run with all ST4 releases. I wouldn't want to add more stuff in here.

Looks good to me, tested it and works great! Will submit to package control today!

Thanks again,@deathaxe@rchl