Sublime Syntax
Sublime Text/Merge syntax highlighting definition
*.sublime-syntax
Validate
Check your file against this schema
Opens the validator with this schema already loaded. Paste your
*.sublime-syntax and it validates in your browser — nothing is uploaded.
Reference
Fields
Generated directly from the schema, following local
$refs, to two levels of nesting.
| Field | Type | Description |
|---|---|---|
name | string | This defines the name shown for the syntax in the menu. It’s optional, and will be derived from the file name if not used. |
file_extensions | array<string> | A list of strings, defining file extensions this syntax should be used for. Extensions listed here will be shown in file dialog dropdowns on some operating systems. If a file does not have a basename, e.g. .gitignore, the entirety of the |
hidden_file_extensions | array<string> | A list of strings, also defining file extensions this syntax should be used for. These extensions are not listed in file dialogs. |
first_line_match | string | When a file is opened without a recognized extension, the first line of the file contents will be tested against this regex, to see if the syntax should be applied. |
scoperequired | string | The default scope assigned to all text in the file |
version | integer | — default: 2one of: 1, 2 |
extends | oneOf | A base syntax (or list of syntaxes) to inherit from, specified using its package path, e.g. Packages/JavaScript/JavaScript.sublime-syntax. When using multiple inheritance, parent syntaxes are processed top to bottom and must share the same |
hidden | boolean | Hidden syntax definitions won’t be shown in the menu, but can still be assigned by plugins, or included by other syntax definitions. |
contextsrequired | object | https://www.sublimetext.com/docs/syntax.html#contexts |
variables | object | Variables must be defined at the top level of the .sublime-syntax file, and are referenced within regxes via {{varname}}. Variables may themselves include other variables. Note that any text that doesn’t match {{[A-Za-z0-9_]+}} won’t be |
Audit
What we found in this schema
- Declared draft: draft-07
- Validates cleanly against its own meta-schema.
- 32 properties, 88% carrying a description, max nesting depth 9.
Standards
Specification sections for the keywords in this schema
| Keyword | Document | Section |
|---|---|---|
$comment | JSON Schema Core, draft 2020-12 | §8.3 — Comments With "$comment" |
$id | JSON Schema Core, draft 2020-12 | §8.2.1 — The "$id" Keyword |
$ref | JSON Schema Core, draft 2020-12 | §8.2.3.1 — Direct References with "$ref" |
$schema | JSON Schema Core, draft 2020-12 | §8.1.1 — "$schema" |
anyOf | JSON Schema Core, draft 2020-12 | §10.2.1.2 — "anyOf" |
description | JSON Schema Validation, draft 2020-12 | §9.1 — "title" and "description" |
items | JSON Schema Core, draft 2020-12 | §10.3.1.2 — "items" |
minItems | JSON Schema Validation, draft 2020-12 | §6.4.2 — "minItems" |
minProperties | JSON Schema Validation, draft 2020-12 | §6.5.2 — "minProperties" |
pattern | JSON Schema Validation, draft 2020-12 | §6.3.3 — "pattern" |
patternProperties | JSON Schema Core, draft 2020-12 | §10.3.2.2 — "patternProperties" |
properties | JSON Schema Core, draft 2020-12 | §10.3.2.1 — "properties" |
required | JSON Schema Validation, draft 2020-12 | §6.5.3 — "required" |
type | JSON Schema Validation, draft 2020-12 | §6.1.1 — "type" |
uniqueItems | JSON Schema Validation, draft 2020-12 | §6.4.3 — "uniqueItems" |
Documents
- JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
- JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
- RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.
Source
Attribution
This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.