tc39 / tc39/proposal-json-parseimmutable
Potential backwards compatibility issue with options bag
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 48
- Forks
- 4
- Avg merge
- 1d 1m
- Merged PRs (30d)
- 5
Description
One potential issue to consider is that the current spec ignores the reviver if it's not callable, so newer programs running on old engines might not get the behavior they expect. This is akin to adding a param that was previously ignored, but in this case the author might have different expectations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked ECMAScript JSON.parse specification and the issue's five-comment discussion, focusing on how non-callable revivers are handled and how the proposed options bag affects older engines. Done means the backwards-compatibility concern has a documented resolution in the proposal or its specification discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100