Skip to content

fenced-terraform syntax falling back to invalid json #765

@SamLR

Description

@SamLR

I really love this package but I've noticed that the fenced-json syntax always embeds the json.terraform syntax that then resolves to invalid.illegal.expected-mapping-key.json for terraform attribute key/value pairs.

The following change in syntaxes/Markdown.sublime-syntax:2737 seems to fix it but I'm unsure whether this is correct in how syntax embedding is supposed to work (I've not really messed with the .sublime-syntax files before)

# syntaxes/Markdown.sublime-syntax:2737
-         source.json.terraform
+         source.terraform

before the fix the scope looks like:
fenced-json-terraform
With the patch applied the scope becomes (and the error syntax highlighting goes away)
fenced-terraform

Metadata

Metadata

Assignees

No one assigned

    Labels

    C: syntaxCategory: syntax definitionbug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions