Syntax: Change scope of contexts

This commit scopes context names `entity.name.class.context` to align kind icon
in 'Goto Symbol' quick panel with that from completion popup.

Completions' KIND_ID is adjusted to ensure both panels display `c` with same
color.

Note: Choosing a right scope is the only way to adjust the kind icon.

Author: deathaxe

Package/Sublime Text Syntax Definition/Sublime Text Syntax Definition.sublime-syntax

@@ -263,7 +263,7 @@ contexts:
           pop: true
         - match: ''
           set:
-            - meta_scope: string.unquoted.plain.out.yaml entity.name.function.context.sublime-syntax
+            - meta_scope: string.unquoted.plain.out.yaml entity.name.class.context.sublime-syntax
             - match: '{{_flow_scalar_end_plain_out}}'
               pop: true
 

Package/Sublime Text Syntax Definition/Symbols - Context.tmPreferences

@@ -3,7 +3,7 @@
 <plist version="1.0">
 <dict>
     <key>scope</key>
-    <string>source.yaml.sublime.syntax entity.name.function.context</string>
+    <string>source.yaml.sublime.syntax entity.name.class.context</string>
     <key>settings</key>
     <dict>
         <key>showInSymbolList</key>

Package/Sublime Text Syntax Definition/syntax_test_sublime-syntax.yaml

@@ -166,7 +166,7 @@ contexts:
 # <- meta.block.contexts keyword.control.flow.contexts.sublime-syntax - meta.block.variables
 
   main:
-# ^^^^ entity.name.function.context.sublime-syntax
+# ^^^^ entity.name.class.context.sublime-syntax
     - include: scope:source.json
 #     ^^^^^^^ string.unquoted.plain.out.yaml keyword.operator.include.sublime-syntax
       apply_prototype: true
@@ -177,15 +177,15 @@ contexts:
 #<- - meta.expect-include - meta.expect-context-list-or-content - meta.expect-context-list
 
   context_name:
-# ^^^^^^^^^^^^ entity.name.function.context.sublime-syntax
+# ^^^^^^^^^^^^ entity.name.class.context.sublime-syntax
     - captures:
 #     ^^^^^^^^ string.unquoted.plain.out.yaml storage.type.captures.sublime-syntax
         1: name
   another_context_name:
-# ^ entity.name.function.context.sublime-syntax
+# ^ entity.name.class.context.sublime-syntax
     - captures:
   another_context_name:
-# ^ entity.name.function.context.sublime-syntax
+# ^ entity.name.class.context.sublime-syntax
 
     - meta_append: true
 #     ^^^^^^^^^^^ storage.modifier.context-extension.sublime-syntax
@@ -390,7 +390,7 @@ contexts: !mytag
 #^^^^^^^ string.unquoted.plain.out.yaml keyword.control.flow.contexts.sublime-syntax
 #         ^^^^^^ storage.type.tag-handle.yaml
   main: !mytag
-# ^^^^ entity.name.function.context.sublime-syntax
+# ^^^^ entity.name.class.context.sublime-syntax
 #       ^^^^^^ storage.type.tag-handle.yaml
     - match: !mytag abc+
 #     ^^^^^ keyword.other.match.sublime-syntax

plugins/syntax_dev/completions.py

@@ -54,7 +54,7 @@
 )
 TPL_CONTEXT = CompletionTemplate(
     format=sublime.COMPLETION_FORMAT_SNIPPET,
-    kind=(sublime.KIND_ID_KEYWORD, 'c', 'Context'),
+    kind=(sublime.KIND_ID_TYPE, 'c', 'Context'),
     suffix=":\n  ",
 )
 TPL_FUNCTION = CompletionTemplate(
@@ -302,7 +302,7 @@ def _complete_context(self, prefix, locations):
 
         return format_completions(
             [(self.view.substr(r), self.view.rowcol(r.begin())[0] + 1)
-             for r in self.view.find_by_selector("entity.name.function.context")],
+             for r in self.view.find_by_selector("entity.name.class.context")],
             annotation="",
             kind=TPL_CONTEXT.kind,
         )