Change Markdown comment type from JSON to JSON5 to allow comments#840
Closed
sadortun wants to merge 2 commits intoparse-community:gh-pagesfrom
Closed
Change Markdown comment type from JSON to JSON5 to allow comments#840sadortun wants to merge 2 commits intoparse-community:gh-pagesfrom
sadortun wants to merge 2 commits intoparse-community:gh-pagesfrom
Conversation
Contributor
Member
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
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.
Hi !
Fixed a few more comments.
JSON5 resemble much more regular JS objects and in most example it's what we are presenting. I would recommend
```json5to show actual javascript objects```jsonto show actual client/server JSON message