Sublime does not enable extension in correct context about handlebars HOT 4 CLOSED

Edit: I see from reading the readme this may be by design: In which case this could be tagged as an enhancement.

from handlebars.

I haven't heard of Twig yet, but on a quick research it seems that it supports multiple template systems? If that's the case I wouldn't want to hardcode the file type association into the Handlebars package as people who use other templates would be really annoyed that the wrong package is trying to handle their files :) Can you name you file .twig.handlebars?

As for using it inside a HTML script tag, that's a change in the HTML package. It would need to understand that the tag contains Handlebars and load the language definition. I'm not even sure if that package is on Github, if you find it I can try to work with whoever is maintaining it :)

from handlebars.

I guess the html scoping is handled by sublime natively. The scope within a script tag (embedded) is:

text.html.basic source.js.embedded.html

This seems like a narrow enough scope I think? Where there are conflicts in autocompletion (for example 'if'), between raw js and handlebars, ST2 usually displays both options in a dropdown menu. I think this would be acceptable (what do you reckon?)

edit: Similar issue in jQuery snippets bundle - with relevant commit:
aaronpowell/sublime-jquery-snippets#1

As for twig - Is it possible to only enable if the file extension is 'handlebars.twig' rather than just '.twig' (you are right re: twig supporting multiple template systems). I wouldn't want to change the file extension as .twig is an extension which requires compiling (It's a handlebars file written IN twig rather than the inverse).

Cheers

from handlebars.

Added a separate PR - will close this.

from handlebars.