Fix #8729: Make JSON.stringify accept null and undefined replacers - #8732
Merged
Merged
Conversation
Contributor
Author
|
Fixes #8729 |
Member
|
:+1+ |
Member
|
I hate the GitHub app, you know what I meant. |
ghost
mentioned this pull request
Merged
ghost
pushed a commit
that referenced
this pull request
May 23, 2016
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spec: http://www.ecma-international.org/ecma-262/6.0/#sec-json.stringify
split into two signatures for better parameter help experience on the replacer.