graphql-client

graphql-client copied to clipboard

Attribute #[allow(non_camel_case_types)] for enums

1

My graphql scheme contains enums with capital letters values and graphql-client cli generates such code: ```rust #[derive(Eq, PartialEq)] pub enum PagesSortType { #[doc = ""] ID_ASC, #[doc = ""] ID_DESC,...

acelot

Drop syn and quote in graphql_client_codegen?

1

We don't use the nice syn features about reporting errors. The code we generate cannot be mapped back to a precise rust code span, since it depends on the GraphQL...

tomhoule

Add example for type refining fragment

1

PR #181 added support for type refining fragments and was released in version 0.6.0. The existing examples, however, were not augmented to demonstrate how to work with such a fragment....

nirvdrum

Extensions

1

Hi, First of all, awesome library - thankyou!! I know this was opened on #89. The extensions field IS part of the standard (albeit as an optional field), see `https://github.com/graphql/graphql-spec/blob/main/spec/Section%207%20--%20Response.md`...

tculshaw

Problem with nonnull fields and @include directives

3

I have following request: ```graphql query ListRuns($detailed: Boolean!) { submissions { id, problem @include(if: $detailed), score @include(if: $detailed), status @include(if: $detailed) { kind, code }, toolchainName @include(if: $detailed) } }...

MikailBag

Generate common types for named types in schema

5

I'm working with an API that uses the GraphQL-standard `errors` field for critical failures and its own `UserError` type for validation errors. Every operation in this API can respond with...

nirvdrum

Extend keyword?

3

I have a type such as: ``` type A { field_public: Int } ``` Later on in the same file, I write: ``` extend type A { field_private: Int }...

lthiery

GraphQLQuery macro creates incompatible types for fragments shared between queries

10

I'm using Github v4 API to query some repo state and have some fragments like this: ```graphql fragment PullRequestView on PullRequest { # ... } fragment IssueView on Issue {...

yuyoyuppe

Always normalize type/field names

4

The normalization feature is a burden to maintain, we should always normalize field names to snake case and type names to camel case to respect rust conventions.

tomhoule

Cohesiveness between GraphQLQuery struct, its Variables and ResponseData

2

With current APIs it is possible to have mismatch between the struct, `Variables` and `ResponseData` . Example from the README.md: ```rust let request_body = UnionQuery::build_query(variables); let client = reqwest::Client::new(); let...

tomasol