Updating JSON runtime format documentation #909
Conversation
This file contains 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
The documentation as it is is outdated and has never been fully complete, this is a first stab at filling in the blanks.
Typo fix and a single word changed
Forgot to escape the pipe operators, breaking the table
Don't know where I thought I saw strings getting cast to bools, but it's not in the source code.
…format.md" This reverts commit b80effe.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This updates the documentation of the JSON runtime format.
Both the documentation and the comments in the serializer were outdated, and the documentation was missing descriptions of crucial parts of the runtime. There has previously been an attempt to update the documentation more comprehensively, but this is just an update and filling out of what already exists.
Closes #882