Skip to content
Source on GitHubVisitors

JSON editor

`.json` files checked for JSON's own mistakes and against the JSON Schema their `$schema` names, with completion and descriptions from it

Editor · origin tag editor/json · Editors

Availability

Availability per host
HostStateHow to get it
StandaloneAvailableInstall from v0.1.3826-alpha
DesktopNot plannedNot planned
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Not described yet.

Why a specialized view helps

Not described yet.

File formats

Not described yet.

Screenshots

The JSON editor on a document that breaks the schema beside it: the keys and values coloured, a red marker in the gutter on each line the schema rejects and the yellow warning on the deprecated `verbose`, wavy underlines under the offending values, and the status line reading **Saved**, **7 errors, 1 warning** and the schema's title *Service settings*.

Standalone, at 2bd8441

What is visible: The JSON editor on a document that breaks the schema beside it: the keys and values coloured, a red marker in the gutter on each line the schema rejects and the yellow warning on the deprecated `verbose`, wavy underlines under the offending values, and the status line reading **Saved**, **7 errors, 1 warning** and the schema's title *Service settings*.

Why it matters: A JSON file is checked against the JSON Schema its $schema names while it is typed, so a key the schema rejects or a deprecated setting is marked on its line before the file is ever loaded by the program that reads it.

Licence: Apache-2.0

Background

Focus areas

Not in a focus area yet.

Sources