You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When comparing a query where the expected type has been extended to exactly match the actual type, the comparator is currently reporting a change.
Can someone confirm if this is correct? I would have expected the two queries to show no changes.
Expected:
type Query {
}
extend type Query {
test(id: String!): String!
}
Actual:
type Query {
test(id: String!): String!
}
Output:
`⏳ Checking for changes...
🎉 Done! Result:
Detected the following changes between schemas:
✅ Field test was added to object type Query
`
The text was updated successfully, but these errors were encountered:
andyce1010
changed the title
Extended Query being reported as a different to a non-extendededed Query, when it is actually the same.
Extended Query being reported as a different to a non-extended Query, when it is actually the same.
Dec 13, 2021
Just to confirm, are expected and actual the two schemas you're comparing?
I'd probably expect the diff between those to show no changes either. This might also be behaviour from the graphql-ruby gem itself. I'd suggest running GraphQL::Schema.from_definition(schema).to_definition to see what it outputs for the schema with extend
When comparing a query where the expected type has been extended to exactly match the actual type, the comparator is currently reporting a change.
Can someone confirm if this is correct? I would have expected the two queries to show no changes.
Expected:
Actual:
Output:
`⏳ Checking for changes...
🎉 Done! Result:
Detected the following changes between schemas:
✅ Field
test
was added to object typeQuery
`
The text was updated successfully, but these errors were encountered: