Simple example:
li: custom-link.has-text-primary(to="/")
Grammar is here: https://github.com/davidrios/pug-tmbundle
The li is correctly categorized as entity.name.tag.pug. custom-link is incorrectly categorized as text.pug If you copy the same grammar into a different editor and use their text mate engine, custom-link is correctly categorized as entity.name.tag.pug.
In the grammar, this is the rule that is not getting applied correctly:
"tag_name": {
"begin": "([#!]\\{(?=.*?\\}))|(\\w(([\\w:-]+[\\w-])|([\\w-]*)))",
"end": "(\\G(?<!\\5[^\\w-]))|\\}|$",
"name": "meta.tag.other entity.name.tag.pug",
"patterns": [
{
"begin": "\\G(?<=\\{)",
"end": "(?=\\})",
"name": "meta.tag.other entity.name.tag.pug",
"patterns": [
{
"match": "{",
"name": "invalid.illegal.tag.pug"
},
{
"include": "source.js"
}
]
}
]
},
Originally found in microsoft/vscode#65983
Simple example:
Grammar is here: https://github.com/davidrios/pug-tmbundle
The
liis correctly categorized asentity.name.tag.pug.custom-linkis incorrectly categorized astext.pugIf you copy the same grammar into a different editor and use their text mate engine,custom-linkis correctly categorized asentity.name.tag.pug.In the grammar, this is the rule that is not getting applied correctly:
Originally found in microsoft/vscode#65983