I’ve seen the ideas of doing client-side @nonnull, but is there a notion of doing @nullable? There’s basically a query I am doing, which has a bunch of fields, and one of those fields is non-null. However this has happened to be null sometimes, due to some backend service experiencing some issues or something like that, which then breaks the entire query. In this particular case, it’d actually be totally fine client-side to not get this data and just render the rest. Is there something I am missing that I can do aside from editing the schema file to remove that

!

from that specific query response type?

There's something like that in client controlled nullability. It's called error-boundaries

Interesting, yeah that’s gonna be nice to be there for 4.x. For now do you find any issue with simply editing the schema itself as I download it to remove the

!

?

Yup, that should work

Yeah definitely, since if they don’t the other clients will also be getting broken data. I mostly wanna do this now for my dev environment so that I don’t need to change too much code to continue testing something else, and will try to address this in the real schema. Thanks for the help! 🤗