Using a different GraphQL client

I’m fully on board with standardizing on a single set of tools, no need to have that argument in this thread :slight_smile:

I would strongly suggest taking a look at gqless, though. I saw another thread about providing first class TypeScript support:

As you work towards a 1.0, I think the idea of having explicitly declared GraphQL queries in the client will feel very redundant (and error prone) if it is instead possible to simply reference an object, access its properties, and have the GQL query constructed on the fly. That was, among other things, the magic of ActiveRecord. And it would be great to see it in RedwoodJS.