There is one more type of query
checkTypePassword(name: String!, pwd: String!): Type, that can return
This case won’t occur , if there is no response in a list then we don’t return null but empty list
We can have this case
[null] if there is some in the marshaling of the response. You should check for the null value before accessing every item from the response.
We haven’t added constraints on the query response like
[Type!]! to keep API flexible even though the first case is unlikely to occur. For example if we now enforce these conditions and in future we allow null response instead of
 , then that will be breaking change.
So, I suggest you to check for
null value before accessing a list or items in a
list of the response.