Merged
Conversation
- add terminology for line endings and insignificant whitespace - state that comments are informational only and must not affect consumed JSON values clarify single-line comment behavior to end at line ending - expand single-line example to show case at the end of a line
Co-authored-by: hattesen <hattesen@users.noreply.github.com>
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addreses #9 and some other potential confusion with comment syntax.
Note that the name "Multi-line" was kept as section title since that's the terminology used in EcmaScript.
This PR will:
@hattesen, I added you as co-author of 03b0dfd since I used your snippet to illustrate the invalid nesting syntax. I can remove the mention if you prefer before merging.