Hello, I’m wondering if what i came across is a normal behaviour or a bug. Let’s say I have the following schema: interface EntityInBoxInterface { id: ID! name: String! @search(by: [term]) } type Object implements EntityInBoxInterface { data: String } type Face implements EntityInB…

Using unions and interfaces and end up with non-nullable field not present

pshaddel (Poorshad Shaddel) October 12, 2021, 1:08pm 9

I was encountered another bug related to union but it was ignored.

1 Like

Topic		Replies	Views
No input field null validation on non nullable fields GraphQL status:accepted , kind:bug , ticket:created	30	5611	March 22, 2022
GraphQL permits null fields on mutation GraphQL kind:bug	5	2293	July 29, 2021
GraphQL: "Non-nullable field was not present in result" on identically named fields under interface Dgraph dgraph , status:accepted , kind:bug , area:graphql	6	884	August 21, 2020
Non-nullable field was not present in result from Dgraph GraphQL kind:bug	1	883	February 23, 2021
Union types in GraphQL Dev graphql , rfc	13	8666	December 14, 2024