add sublime-syntax.json

[Freed-Wu]

sublimehq/sublime_text#6023

[Freed-Wu]

Fixed.

[Freed-Wu]

Add URL, pattern, descriptions.

[EmilyGraceSeville7cf]

@Freed-Wu, you can also add completion for some common scopes using this technique:

• list common scopes as properties
• allow additional properties via additionalProperties to permit any not common scopes

P.S. to fix issue with build failure change test/sublime-syntax/cmd-help.sublime-syntax to test/sublime-syntax/cmd-help.sublime-syntax.json or test/sublime-syntax/cmd-help.json.

[Freed-Wu]

Add extension for test sublime syntax. Remove addionalProperties to permit any not common scopes.

[Freed-Wu]

Fixed.

[Freed-Wu]

Can scope name have some recommended values? https://www.sublimetext.com/docs/scope_naming.html lists the recommend values for many scope names and corresponding documents.

[hyperupcall]

@Freed-Wu If scope values are strings and you want to recommend ones in particular, I think you can use a pattern like this:

{
  "oneOf": [
    {
      "type": "string",
      "enum": ["one", "two", "three"]
    },
    {
      "type": "string"
    }
  ]
}

[madskristensen]

Is this ready to be merged?

[Freed-Wu]

If scope values are strings and you want to recommend ones in particular

Can we provide a description for every scope?

Is this ready to be merged?

If any recommended value for scope is not recommended, it should be enough.

[hyperupcall]

@Freed-Wu I'm not sure. What comes to mind is something like this:

{
  "oneOf": [
    {
      "type": "string",
      "enum": ["scope1"],
      "description": "Description 1"
    },
    {
      "type": "string"
      "enum": ["scope2"],
      "description": "Description 2"
    },
    {
      "type": "string"
    }
  ]
}

But I'm not sure if it actually works, you can test if it does, though.

[hyperupcall]

@Freed-Wu My earlier comment seems incorrect, I have recently found out that you need to use anyOf instead of oneOf.

[Freed-Wu]

Can scope name have some recommended values?

It is hard because scope, meta_scope, captures can be many scope names like

https://github.com/vuejs/vue-syntax-highlight/tree/HTML.yaml#L280:

# ...

contexts:
  # ...
  style-type-attribute:
    - match: (?i)\btype\b
      scope: meta.attribute-with-value.html entity.other.attribute-name.html
      set:
        - meta_content_scope: meta.tag.style.begin.html meta.attribute-with-value.html
        - match: =
          scope: punctuation.separator.key-value.html
          set:
            - meta_content_scope: meta.tag.style.begin.html meta.attribute-with-value.html
            - include: style-type-decider
        - match: (?=\S)
          set: style-css

That is, if we want to recommend scope_a, scope_b, scope_c, any combination of scope_a, scope_b, scope_c is legal.

[github-actions]

This PR is stale because it has been open 60 days with no activity. Comment or this will be closed in 7 days.

[hyperupcall]

CI was failing because AJV Strict Mode caught multiple errors in the schema. I have made fixes and I will merge the result unless anybody thinks otherwise