Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JSON] Rewrite syntax #3097

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

[JSON] Rewrite syntax #3097

wants to merge 1 commit into from

Commits on Jun 1, 2022

  1. [JSON] Rewrite syntax

    - Using inheritance split up `JSON.sublime-syntax` into:
        - `JSON.sublime-syntax` with `scope:source.json`
        - `JSONC.sublime-syntax` with `scope:source.json.jsonc`
        - `JSON5.sublime-syntax` with `scope:source.json.json5`
        - `JSON_dotNET.sublime-syntax` with `scope:source.json.json-dotnet`
    - Add many more file extensions for `JSON` & `JSONC`:
        - add doc links to extensions where applicable as a reference to be
          able to more quickly verify that they (still) use said syntax
          flavor
    - JSON:
        - Make use of newer syntax features including those only available
          in `version: 2` syntaxes
        - Make use of `variables` (with optimizations provided by @deathaxe
          and regex patterns provided by @Thom1729)
        - Context names now more closely match the naming scheme of other
          (recently re-written) default syntaxes
        - (correctly formatted) JSON code can now be prettified or minified
          via the context menu or the command palette. JSON code can
          optionally be auto-prettified on pre save events.
        - highlight leading, trailing & multiple commas as invalid
        - only allow exactly one structure (object, array) or value
          (constant, number, string) at top level (thanks to @keith-hall)
        - links (`meta.link.inet`) and email addresses (`meta.link.email`) are
          scoped the same as in Markdown (thanks to @deathaxe)
    - JSONC:
        - highlight some files by default as `JSONC` (as decided by
          @jskinner in sublimehq#285)
        - highlight leading & multiple commas as invalid, trailing as valid
        - scope empty block comments as such
        - support syntax based folding of ST4131+,
          compare sublimehq#3291
    - JSON5:
        - explicitly pos numbers, hexadecimal ints, Infinity and NaN
        - single quoted strings
        - more escape chars for strings
        - ECMA identifierName as object keys (regexes thanks to @Thom1729)
            - scoped as plain unquoted strings (thanks to @Thom1729)
            - support string interpolation (thanks to @deathaxe)
        - line continuation in strings (with tests thanks to @keith-hall)
    - JSON.NET:
        - support requested by @keith-hall,
          built with feedback from @michaelblyons
    - Objects:
        - Highlighting speed improvements for empty objects (thanks to
          @FichteFoll)
        - Make `mapping.*` contexts more modular
    - Arrays:
        - Highlighting speed improvements for empty arrays (thanks to
          @FichteFoll)
    - Numbers:
        - Correctly scope number signs with `constant.numeric.sign` instead
          of `keyword.operator.arithmetic`
        - Significantly improve number highlighting (thanks to @deathaxe)
    - Completions:
        - completions have been added for language constants, including kind info
          and details (with links to docs)
            - `null`, `false`, `true` for JSON
            - `Infinity` and `NaN` for JSON5
    - Settings:
        - a `default_extension` is now set for all JSON flavors
    - Symbol index:
        - with an object structure at the top-level, only top-level keys
          within now show up in the index (including tests for symbols and
          syntax)
    - Tests:
        - test files now test the base scope
        - Significantly extend tests to cover more parts of the syntaxes
        - Split original test file into logical parts
        - Add indentation tests for:
            - `json`, `json5` & `jsonc`
            - `mapping` (objects), `sequence` (arrays)
        - Add symbols tests for:
            - top-level keys of object structures (thanks to deathaxe)
            - languages: `json`, `json5` & `jsonc`
        - Fix tests for `meta.mapping meta.mapping.*`
    - Leave `JSON` headers in `Markdown` as `json` only, but split up fenced
      code blocks into `json`, `json5` & `jsonc` to behave similarly to
      `GitHub Flavored Markdown`
    
    BREAKING CHANGES:
    
    - JSON does not have values that can be set via an inline calculation
      with the help of operators, but only simple number values. Scopes for
      number signs have changed from being `keyword.operator.arithmetic` to
      `constant.numeric.sign`. Color scheme authors should add this, should
      it be missing.
    - The `JSON.sublime-syntax` now marks comments as `invalid`, third party
      plugin authors should instead target `JSONC.sublime-syntax` to keep
      the user experience as-is.
    - Indexed symbols (i.e. top-level keys in JSON object structures) are
      scoped as `source.json meta.mapping.key - (meta.mapping.value meta.mapping.key | meta.sequence.list meta.mapping.key)`.
      Color scheme authors should add special highlighting to differentiate
      them from other keys.
    
    - fix sublimehq#285
    - address sublimehq#421 (thanks to @FichteFoll)
    - address sublimehq#481 to remove incompatible regex patterns according
      to @wbond
    - address sublimehq#757 to fix line comments for `JSONC` (thanks to
      @keith-hall)
    - address sublimehq#2430 using sort-order (as requested by @deathaxe)
    - address sublimehq#2711 with regards to `constant.language.null`
      vs. `constant.language.empty` (thanks to @FichteFoll)
    - address sublimehq#2852 to fix scopes of curly braces & square
      brackets in `JSON` (thanks to @Thom1729)
    - address sublimehq#3228 to fix `punctuation.separator` scopes,
      compare sublimehq#3270
    - address sublimehq/sublime_text#3154 and add symbol tests
    
    Co-authored-by: Ashwin Shenoy <Ultra-Instinct-05@users.noreply.github.com>
    Co-authored-by: Jack Cherng <jfcherng@users.noreply.github.com>
    Co-authored-by: Janos Wortmann <jwortmann@users.noreply.github.com>
    Co-authored-by: Jon Skinner <jps@sublimetext.com>
    Co-authored-by: FichteFoll <FichteFoll@users.noreply.github.com>
    Co-authored-by: Keith Hall <keith-hall@users.noreply.github.com>
    Co-authored-by: Michael B. Lyons <michaelblyons@users.noreply.github.com>
    Co-authored-by: Rafał Chłodnicki <rchl@users.noreply.github.com>
    Co-authored-by: Thomas Smith <Thom1729@users.noreply.github.com>
    Co-authored-by: Will Bond <wbond@users.noreply.github.com>
    Co-authored-by: deathaxe <deathaxe@users.noreply.github.com>
    12 people committed Jun 1, 2022
    Configuration menu
    Copy the full SHA
    14779e2 View commit details
    Browse the repository at this point in the history