Implement a JSTN generator and related APIs #6
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
Pull Request Test Coverage Report for Build 12
💛 - Coveralls |
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 PR introduces a JSTN generator that behaves as described in the specification. Additionally, it clarifies the wording of the specification with regard to the generated pretty format.
Since we now have a way to convert a Type to a serialized form, this PR also implements String(), json.Marshaler, and json.Unmarshaler on Type with the following behavior:
String()method format Type using the concise format.MarshalJSON()produces a JSON string whose value is the JSTN text.UnmarshalJSON()parses a JSTN text string (it returns an error if given a non-string JSON type).