jungho-git/json

JSON

• Shared examples and formatting reference: references/EXAMPLE.md.
• Keep new guidance, snippets, and edits aligned with that file.

Scope

Use this rule when:

• editing .json files
• changing package manifests, tsconfig, API schemas, or config files
• reviewing JSON payloads sent to or received from APIs
• generating or transforming JSON programmatically

JSON edits should preserve syntax, schema, and producer/consumer contracts.

Core Rules

• Use double-quoted keys and string values.
• Do not use comments in .json files.
• Do not leave trailing commas.
• Keep key order stable within objects unless the schema or local convention requires a move.
• Use null explicitly for absent values when the schema defines the key.
• Do not omit required schema keys.
• Minify only for transport or generated output artifacts.

Formatting

• Use 2-space indentation.
• Use one space after a colon and no extra padding.
• Put objects with more than two keys on multiple lines.
• Keep short arrays of scalar values on one line only when readability remains good.
• Never vertically align values or colons.

Validation Focus

• parser validity
• trailing commas and comments
• missing required keys
• type mismatch between schema and value
• producer/consumer contract drift
• lockfile or package-manifest consistency when dependencies change