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
I think the validation rules are not taking default and nullable parameter configurations into account when validating the query.
I have a schema definition that includes a query that takes two parameters both marked as nullable (no ! post-fix) and both with the default value set to null.
The schema looks like this:
typeRecords {
id : Int!
external_id : Int
}
typeQuery {
get_records(id : Int = null, external_id : Int = null) : [Records]
}
schema {
query : Query
}
When I run the following query:
queryTestQuery {
get_records {
id
}
}
I get this error Message:
The `schema.field(get_records)` and `query.field(get_records)` both must expect arguments, not `yes` and `no`"
And when I run the following query:
queryTestQuery {
get_records(id: 1) {
id
}
}
I get this error Message:
The `schema.field(get_records).arity` and `query.field(get_records).arity` must match, not `2` and `1`
The text was updated successfully, but these errors were encountered:
I think the validation rules are not taking default and nullable parameter configurations into account when validating the query.
I have a schema definition that includes a query that takes two parameters both marked as nullable (no
!
post-fix) and both with the default value set tonull
.The schema looks like this:
When I run the following query:
I get this error Message:
And when I run the following query:
I get this error Message:
The text was updated successfully, but these errors were encountered: