Find a better JSON parser or implement our own · glideapps/quicktype#646

2018-03-08T20:03:03.000Z

Required features: * Streaming. We need to process files larger than V8 strings allow. * Preserve property order. * Good and actionable error messages. Our users often have issues with invalid JSON. * Recover from common errors. * Distinguish between integers and floating point numbers. * Span for each non-symbol token - line number and column of start and end. Common errors: * Unquoted keys: `{ foo: "bar" }` * Superfluous commas: `[1, 2, 3,]` * Wrong delimiter: `[ "foo": "bar" ]`, `{ 1, 2, 3 }` Other easily recoverable errors: * `=` (or anything else) instead of `:` in objects: `{ "foo"="bar" }` * Number format stuff, such as no digits before point (`.3`), leading zeros (`0123`), hexadecimals (`0xdeadbeef`)

(12 comments) (2 reactions) (0 assignees)TypeScript (10,867 stars) (968 forks)batch import

good first issue

Description

Required features:

Streaming. We need to process files larger than V8 strings allow.
Preserve property order.
Good and actionable error messages. Our users often have issues with invalid JSON.
Recover from common errors.
Distinguish between integers and floating point numbers.
Span for each non-symbol token - line number and column of start and end.

Common errors:

Unquoted keys: { foo: "bar" }
Superfluous commas: [1, 2, 3,]
Wrong delimiter: [ "foo": "bar" ], { 1, 2, 3 }

Other easily recoverable errors:

= (or anything else) instead of : in objects: { "foo"="bar" }
Number format stuff, such as no digits before point (.3), leading zeros (0123), hexadecimals (0xdeadbeef)

Contributor guide

Tech stack: typescriptnodejs
Domain: clideveloper experience
Issue type: feature
Difficulty: 4
Estimated time: over 1 week
Activity status: stale
Clarity: clear
Prerequisites: TypeScript programmingJSON specificationstreaming I/Oerror handling
Newbie friendliness: 15
Research direction: Investigate the current JSON parser used in quicktype (likely an existing library). Evaluate alternatives like simdjson, rapidjson, or Node.js's native JSON parse with streaming. Review comments and linked issues for prior attempts and maintainer feedback. Assess the project's requirements for streaming, error recovery, and span tracking to propose a custom parser or integrate a suitable library.