> I can think of several ways the language could've been designed to make it easier to write typed query builders.
Would you like to share them? Have you tried submitting your suggestions to the GraphQL core team?
Would you like to share them? Have you tried submitting your suggestions to the GraphQL core team?
Here is a few:
- Less fine-grained field selection - allow for fields selected by default. This would remove some of the need for optionals in languages that aren't able to dynamically create record types on the fly
- Implicit unions and union queries are really annoying to model in both OOP and FP languages. In FP disjoint tagged unions with no inheritance would work better; in OOP common interfaces but no ability to define unions would work better. As it stands, the mix makes it difficult on both language types to support a general schema. Unions based on optional fields (like in GRPC) are probably best-of-both-worlds here.