Given the following type definitions, schema is generated for sorting on the field custom_string_with_param.
This should not occur as that field takes a NonNullable argument.
type Movie {
custom_string_with_param(param: String!): String!
@cypher(statement: "RETURN $param as c", columnName: "c")
}
Excerpt from the schema generated:
\\"\\"\\"
Fields to sort Movies by. The order in which sorts are applied is not guaranteed when specifying many fields in one MovieSort object.
\\"\\"\\"
input MovieSort {
custom_string_with_param: SortDirection
}
We should ensure that custom cypher fields with NonNullable arguments do not have sort schema generated.
We've been able to confirm this bug using the steps to reproduce that you provided - many thanks @mjfwebb! :pray: We will now prioritise the bug and address it appropriately.
Given the following type definitions, schema is generated for sorting on the field
custom_string_with_param
.This should not occur as that field takes a NonNullable argument.
Excerpt from the schema generated:
We should ensure that custom cypher fields with NonNullable arguments do not have sort schema generated.