tc39/proposal-json-parse-with-source issues and pull requests

#47 - Missing bigint type among others

Issue - State: closed - Opened by WebReflection about 2 months ago - 3 comments

#46 - Why is `JSON.rawJSON` limited to primitives only?

Issue - State: open - Opened by airhorns 6 months ago - 2 comments

#45 - Normative: Correctly capture a number negation prefix

Pull Request - State: closed - Opened by gibson042 about 1 year ago

#44 - ShallowestContainedJSONValue misrepresents negative numbers

Issue - State: closed - Opened by gibson042 about 1 year ago

#43 - Editorial: Rename new SDO to distinguish it from grammar nonterminals

Pull Request - State: closed - Opened by gibson042 about 1 year ago

#42 - Meta: Fix TOC auto-expansion

Pull Request - State: closed - Opened by gibson042 almost 2 years ago

#41 - Normative: Suppress source text for JSON parse data modified before access

Pull Request - State: closed - Opened by gibson042 almost 2 years ago - 4 comments

#40 - A polyfill/ponyfill implementation

Issue - State: open - Opened by slavafomin almost 2 years ago - 12 comments

#39 - Reviver can modify holder object, like inserting new object / array, which breaks invariant of parsing information

Issue - State: closed - Opened by Constellation about 2 years ago - 6 comments

#38 - Meta: Constrain README examples

Pull Request - State: closed - Opened by gibson042 about 2 years ago

#37 - Bug in `intToBigInt`?

Issue - State: closed - Opened by rauschma about 2 years ago - 2 comments

#36 - Are there any implementations yet?

Issue - State: closed - Opened by rauschma about 2 years ago - 2 comments

#35 - Assert failed for typedValNode is an ObjectLiteral Parse Node

Issue - State: closed - Opened by jameslahm about 2 years ago

#34 - How to parse bigints when using Response.json() function?

Issue - State: open - Opened by pspraveenkr over 2 years ago - 5 comments

#33 - Meta: Advance to Stage 3

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#32 - Editorial: Rename _value_ alias for clarity

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#31 - Editorial: Rename ArrayElementList to clarify its purpose

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#30 - Editorial: Narrow ShallowestContained to be JSON-specific

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#29 - Stage 3 Specification Review: Waldemar Horwat

Issue - State: closed - Opened by gibson042 over 2 years ago - 2 comments

#28 - Stage 3 Specification Review: Michael Ficarra

Issue - State: closed - Opened by gibson042 over 2 years ago - 1 comment

#27 - [spec] minor editorial tweaks

Pull Request - State: closed - Opened by ljharb over 2 years ago - 1 comment

#26 - Naming of raw text placeholder

Issue - State: closed - Opened by gibson042 over 2 years ago

#25 - Should reviver functions still get a context argument for non-primitive values?

Issue - State: closed - Opened by gibson042 over 2 years ago - 1 comment

#24 - Normative: Restrict source text access to primitive values

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#23 - Meta: Default rendered menu items to expanded

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#22 - Add support for raw JSON serialization via JSON.rawJSON

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#21 - Correctly propagate and visit parse nodes

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#20 - Rebase against current ECMA-262

Pull Request - State: closed - Opened by gibson042 over 2 years ago

#19 - Reusability of raw serialization mechanism

Issue - State: closed - Opened by gibson042 about 3 years ago - 2 comments

#18 - bikeshedding the mechanism for serialization

Issue - State: closed - Opened by bakkot about 3 years ago - 7 comments

#17 - bigint ergonomics of user-function vs options-object

Issue - State: closed - Opened by kaizhu256 about 4 years ago - 1 comment

#16 - performance impact with 1-million json.parse calls

Issue - State: closed - Opened by kaizhu256 over 4 years ago - 1 comment

#15 - Advance to stage 4

Issue - State: open - Opened by gibson042 over 4 years ago - 3 comments

#14 - Advance to stage 3

Issue - State: closed - Opened by gibson042 over 4 years ago - 3 comments

#13 - Meta: Use GitHub Actions to publish rendered spec text

Pull Request - State: closed - Opened by gibson042 almost 5 years ago - 1 comment

#12 - Extend this proposal to include serialization?

Issue - State: closed - Opened by gibson042 almost 5 years ago - 10 comments

#11 - Supply an array of keys for understanding value context?

Issue - State: open - Opened by gibson042 almost 5 years ago - 3 comments

#10 - Expose position and/or input of source text?

Issue - State: open - Opened by gibson042 almost 5 years ago - 12 comments

#9 - How to reference JSON parse nodes

Issue - State: closed - Opened by gibson042 almost 5 years ago

#8 - Update README.md to match spec text

Pull Request - State: closed - Opened by gibson042 almost 5 years ago

#7 - Requirements for stage 2

Issue - State: closed - Opened by codehag almost 5 years ago - 1 comment

#6 - cookbook scenario to JSON.parse bigint in schema-less data

Issue - State: closed - Opened by kaizhu256 almost 5 years ago - 5 comments

#5 - add an options object to JSON.parse and JSON.stringify

Issue - State: closed - Opened by allenwb about 5 years ago - 16 comments

#4 - Move repo to tc39 org

Issue - State: closed - Opened by mathiasbynens about 6 years ago - 1 comment

#3 - What about object/class as argument ?

Issue - State: closed - Opened by lifaon74 about 6 years ago - 5 comments

#2 - Advance to stage 1

Pull Request - State: closed - Opened by mathiasbynens about 6 years ago

#1 - Expose via new callback argument vs. new function

Issue - State: closed - Opened by gibson042 about 6 years ago - 4 comments

GitHub / tc39/proposal-json-parse-with-source issues and pull requests