RFC 8259 JSON Formatting, Validation, and Common Syntax Errors
Fix trailing commas, unquoted keys, unescaped control characters, and single-quote errors in JSON payloads with exact line and column diagnostics.
Engineering Summary & Key Takeaways
- IETF RFC 8259 strictly requires double-quoted property names and forbids trailing commas, comments, single-quoted strings, and unescaped control characters (U+0000 to U+001F).
- JSONC (JSON with Comments) is popular in IDE configuration files (like tsconfig.json) but must be stripped of //, /* */, and trailing commas before passing to JSON.parse() or HTTP APIs.
- Recursive alphabetical object key sorting produces deterministic JSON output for clean Git diffs while preserving array element order.
- Never paste production JWTs, API keys, or customer payloads into server-backed JSON formatters; local Web Worker parsing keeps sensitive payloads inside volatile browser memory.
1. Strict IETF RFC 8259 JSON Grammar Rules
JavaScript Object Notation (JSON) is standardized by IETF RFC 8259 and ECMA-404. Although JSON syntax was inspired by JavaScript object literals, the JSON specification is deliberately much stricter so parsers in C, Rust, Go, Python, and Java can decode payloads deterministically.
A valid JSON document may contain only six data types: objects ({ ... }), arrays ([ ... ]), double-quoted UTF-8 strings ("..."), IEEE 754 numbers (without leading zeros, NaN, or Infinity), booleans (true or false), and null.
| Construct | JS / JSONC Example | Valid in RFC 8259 JSON? | Required RFC 8259 Fix |
|---|---|---|---|
| Trailing Comma | {"a": 1,} | Invalid | Remove comma before closing } or ] |
| Line or Block Comments | // comment or /* note */ | Invalid | Strip comments outside quoted strings |
| Unquoted Property Keys | {service: "api"} | Invalid | Wrap all keys in double quotes: {"service": "api"} |
| Single-Quoted Strings | {'env': 'prod'} | Invalid | Replace outer single quotes with double quotes |
| Special Number Literals | NaN, Infinity, 0xFF, .5 | Invalid | Use finite base-10 decimals (e.g., 0.5, null) |
| Unescaped Newline in String | "line1 line2" | Invalid | Escape control characters as \n, \r, \t, or \uXXXX |
2. Pinpointing Line and Column Syntax Errors and Repairing JSONC
When a 5,000-line API payload fails with a generic SyntaxError, locating a single stray comma or unescaped quote manually wastes valuable debugging time. FetchToolKit combines native parser error offsets with a deterministic RFC 8259 lexical scanner to highlight the exact 1-based Line and Column number with a visual caret pointer (^).
When migrating IDE configuration files (such as VS Code settings.json or tsconfig.json) into strict JSON consumers, a string-aware state machine must strip // and /* */ comments and trailing commas only when outside double-quoted string literals—ensuring URLs like "https://fetchtoolkit.com" are never corrupted.
// Invalid in RFC 8259 (contains comment + trailing comma):
{
// Webhook target URL
"webhookUrl": "https://fetchtoolkit.com/hooks/v1",
"retries": [1, 2, 5,],
}
// Valid RFC 8259 Output after Auto-Fix:
{
"webhookUrl": "https://fetchtoolkit.com/hooks/v1",
"retries": [1, 2, 5]
}3. Recursive Key Sorting for Git Diffs vs. Minification for Wire Transfer
Two JSON objects with identical key-value pairs serialized in different property orders produce noisy, multi-hundred-line Git diffs. Enabling Sort Keys (A-Z) recursively sorts every object key using lexicographical comparison while leaving array element order untouched.
Once debugging is complete, switching to Minify mode removes all formatting indentation and line breaks—typically reducing formatted JSON byte size by 15% to 35% for HTTP request bodies and database columns.
Frequently Asked Questions
Why is pasting production JSON into server-based formatters a security risk?
Server-side JSON formatters transmit your payload over the network, where bearer tokens, session cookies, internal endpoints, and customer PII can be captured in reverse-proxy logs or database caches. FetchToolKit formats and validates JSON strictly inside a local Web Worker (json.worker.ts) on your device.
Does sorting JSON keys break JSON arrays?
No. Array index order carries semantic meaning in JSON, so FetchToolKit only reorders object property keys ({ "b": 1, "a": 2 } -> { "a": 2, "b": 1 }) while preserving the exact sequence of elements inside every array.