Skip to content

Commit

Permalink
Syntax: Use plain-out rule for scope matching
Browse files Browse the repository at this point in the history
The comment seems to have been copy-pasted from the include list, as I
can't imagine how a scope name in `expect_scope` would ever be part of
a context-list.

Fixes #307.
  • Loading branch information
FichteFoll committed Nov 2, 2020
1 parent 5c65b4a commit 9c41371
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -302,8 +302,7 @@ contexts:
- match: (?={{ns_plain_first_plain_out}})
set:
- meta_scope: meta.scope.sublime-syntax string.unquoted.plain.out.yaml
- match: '{{_flow_scalar_end_plain_in}}'
# use plain-in for when inside of an 'context-list', although not always accurate
- match: '{{_flow_scalar_end_plain_out}}'
set:
- match: \n?
scope: meta.scope.sublime-syntax
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -271,6 +271,9 @@ contexts:
# ^^^^^^^^^^^^^^^^^^^ meta.scope.sublime-syntax string.unquoted.block.yaml
# ^ punctuation.separator.scope-segments.sublime-syntax

scope: meta.interface.xxx, entity.name.xxx, etc.xxx
# ^ string.unquoted.plain.out.yaml

- embed: scope:source.test
# ^^^^^ string.unquoted.plain.out.yaml keyword.operator.include.sublime-syntax
# ^^^^^ support.type.include.sublime-syntax
Expand Down

0 comments on commit 9c41371

Please sign in to comment.