I'm only first level brown belt in Subgraph/GraphQL so not even sure a feature like this makes sense for the graph-client, but here goes.
I'm finding myself writing duplicate queries to handle different where clauses, and obviously this feels redundant and clunky. Doing a bit of research I came across this interesting article which describes a generic way to handle passing different filter clauses into a single query from a node based GraphQL api client.
https://dev.to/mgustus/filtering-graphql-query-using-typescript-and-typeorm-2l49
Curious if this, or something like it, would make sense for the graph-client?
I'm only first level brown belt in Subgraph/GraphQL so not even sure a feature like this makes sense for the graph-client, but here goes.
I'm finding myself writing duplicate queries to handle different
whereclauses, and obviously this feels redundant and clunky. Doing a bit of research I came across this interesting article which describes a generic way to handle passing differentfilterclauses into a single query from a node based GraphQL api client.https://dev.to/mgustus/filtering-graphql-query-using-typescript-and-typeorm-2l49
Curious if this, or something like it, would make sense for the graph-client?