Is it possbile to generate queries from "query" definitions? about zeroql HOT 9 CLOSED

If you want to generate a wrapper for your existing GraphQL queries that were written via GraphQL syntax use StrawberryShake

The ZeroQL allows you to write GraphQL queries with C# that's all. It doesn't generate queries from GraphQL files.

from zeroql.

I see. I just tried StrawberryShake and it just produces invalid 43mb file with almost 700k locs. This is utterly deranged.

I also tried @graphql-codegen/c-sharp npm package and as anything that comes from garbage script ecosystem it doesn't work either.

Your library is the only one that just works so I guess I'm sticking with it.

Can you give some pointers on how I can translate graphql query/mutation/fragments using your library? As far as I can see the transformation can be done, it's just that spec file needs to be parsed again so types can be checked.

I believe something like extension methods to a Query/Mutation types could be generated.

Also, as your library is already supporting fragments, I think it's possible to translate gql fragments definitions too.

from zeroql.

Your example:

query QueryName($queryParams) {
  actualQueryToCall($queryParams) {
    ...thingsToReturn
  }
}

It would look like that:

var client = new YourZeroQLClient(httpClient);
var queryParams = // some value
var response = await client.Query("QueryName", q => q.ActualQueryToCall(queryParams, o => o.ToThingsToReturn()))

// ...
public static class ThingsToReturnExtensions
{
   [GraphQLFragment]
    public static SomeReturnType ToThingsToReturn(this QueryType value)
    {
        return new SomeReturnType(value.Id, value.Name);
    }
}

The YourZeroQLClient is the client name specified during the generation. Basically, that's all.

from zeroql.

Thanks. I should have said automatically*. It's just there are so many of these queries that I'd rather tinker with your library and possibly do some pr if successful than write all that by hand.

from zeroql.

Oh, you meant automatically.

Potentially you could create a new CLI or extend the ZeroQL CLI tool that will parse existing graphql files with graphql parser and then generate calls for the "presumably existing" ZeroQL client.

In theory, it should not require any type information — just translation from raw GraphQL string to raw C# string. However, there are lots of places where something can go wrong.

from zeroql.

To encapsulate the query you can use GraphQL request syntax.

However, here comes another issue. You encapsulate the query and because of it can not return the anonymous type. As a result, you need to generate stub classes to map results to. The StrawberryShake does it.

from zeroql.

I see. Thank you for the insights.
One more question: how to send custom headers with the request? From the code I see, custom QueryPipeline should be created?

from zeroql.

how to send custom headers with the request? From the code I see, custom QueryPipeline should be created?

The client constructor requires the HTTP client. You can set any headers to this HTTP client at any moment, or you can implement IHttpHandler and pass it to the constructor to intercept and modify the HTTP call.

from zeroql.

Here you can find the example for IHttpHandler. It is a new feature and doesn't have documentation yet.

from zeroql.