Nope. Still present bug/feature depending on who is talking about it.
I just took the ! off from almost every edge. Especially any edge that might return null because of child auth rules.
I think there is another topic if not this one discussing the possibility of changing the schema requiring input but not throwing an error of there is not an output. This is another thing that should be a quick fix and bring a lot of value, but no one seems focused on developing the GraphQL API endpoint right now from what I have been seeing.