Remove contradictory language #535
Merged
Conversation
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
It is contradictory to state that a server "may omit any of the built-in scalars" and then state that it MUST NOT include a built-in scalar if it doesn't use it.
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
IvanGoncharov
added
the
✏️ Editorial
leebyron
added a commit
that referenced
this pull request
Jul 23, 2019
Attempts a more holistic fix to #535 which unifies language around built-in scalars and serialization, shortening the intro to this section in the process.
leebyron
added a commit
that referenced
this pull request
Jul 23, 2019
Attempts a more holistic fix to #535 which unifies language around built-in scalars and serialization, shortening the intro to this section in the process.
leebyron
added a commit
that referenced
this pull request
Jan 10, 2020
Attempts a more holistic fix to #535 which unifies language around built-in scalars and serialization, shortening the intro to this section in the process.
leebyron
added a commit
that referenced
this pull request
Jan 10, 2020
Attempts a more holistic fix to #535 which unifies language around built-in scalars and serialization, shortening the intro to this section in the process.
leebyron
added a commit
that referenced
this pull request
Jan 10, 2020
* Improve clarity of scalar types Attempts a more holistic fix to #535 which unifies language around built-in scalars and serialization, shortening the intro to this section in the process. * Add clarifying note about Enum leafs in Scalar section
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.
It is contradictory to state that a server "may omit any of the built-in scalars" and then state that it MUST NOT include a built-in scalar if it doesn't use it.