Remove paragraph about the robustness principle #40
+0
−7
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
jakobmerrild
added a commit
to jakobmerrild/graphql-scalars
that referenced
this pull request
Dec 2, 2025
There's a separate suggestion to update the guide lines to not mention being liberal in what is accepted for inputs. See: graphql#40
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow up from #26 (comment)
I find the Robustness principle to be generally harmful for the reasons outlined in this RFC.
It also complexifies the handling of scalars because it breaks the symmetry between output and input wire formats.
GraphQL being generally typesafe and the number of GraphQL servers being limited, I think we can be strict about what we accept.