Skip to content

field merging - field TYPES must not differ #979

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 5, 2023
Merged

field merging - field TYPES must not differ #979

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e70b5a0
field merging - field TYPES must not differ
romanivantsov Aug 3, 2022
fedd89a
Update spec/Section 5 -- Validation.md
rivantsov Dec 7, 2022
d3f61c0
lint
leebyron Jan 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/Section 5 -- Validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -556,8 +556,8 @@ fragment safeDifferingArgs on Pet {
```

However, the field responses must be shapes which can be merged. For example,
scalar values must not differ. In this example, `someValue` might be a `String`
or an `Int`:
leaf types must not differ. In this example, `someValue` might be a `String` or
an `Int`:

```graphql counter-example
fragment conflictingDifferingResponses on Pet {
Expand Down