I love GQL, but making things optional by default in the schema was the stupidest decision they could've made. Also the issue with GQL is that FE devs love to

I love GQL, but making things optional by default in the schema was the stupidest decision they could've made. Also the issue with GQL is that FE devs love to copy+paste giant queries that just get everything because it's "convenient", or build up a query while building/testing something and then go on to use that query, including fields that don't eventually get used in the final work. What GQL->consumer ecosystem really needs is something that can check if a field is ever actually accessed in the code or not, something TS/compilation-wise would work. That way the query can be narrowed down to what's actually used in code.