Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update reader and writer for RFC 7159. #773

Merged
merged 1 commit into from
Jan 18, 2016
Merged

Update reader and writer for RFC 7159. #773

merged 1 commit into from
Jan 18, 2016

Conversation

JakeWharton
Copy link
Contributor

This allows for top-level value types without the requirement of leniency.

swankjesse added a commit that referenced this pull request Jan 18, 2016
Update reader and writer for RFC 7159.
@swankjesse swankjesse merged commit af68d70 into master Jan 18, 2016
@JakeWharton JakeWharton deleted the jw/rfc7159 branch January 18, 2016 20:27
sebasjm pushed a commit to sebasjm/gson that referenced this pull request Mar 11, 2018
Update reader and writer for RFC 7159.
Marcono1234 added a commit to Marcono1234/gson that referenced this pull request Aug 25, 2020
RFC 7159 allows any top-level value (not only arrays or objects) [0],
however when google#773 added this functionality it appears the author forgot
to update the documentation of these classes.

[0] https://tools.ietf.org/html/rfc7159#appendix-A
> Changed the definition of "JSON text" so that it can be any JSON
> value, removing the constraint that it be an object or array.
eamonnmcmanus pushed a commit that referenced this pull request Aug 7, 2022
* Fix JsonReader / JsonWriter documentation regarding top-level value

RFC 7159 allows any top-level value (not only arrays or objects) [0],
however when #773 added this functionality it appears the author forgot
to update the documentation of these classes.

[0] https://tools.ietf.org/html/rfc7159#appendix-A
> Changed the definition of "JSON text" so that it can be any JSON
> value, removing the constraint that it be an object or array.

* Fix missing space
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants