Trim down prefixing of generated items about graphql-client HOT 4 CLOSED

Should we do no prefix by default and let the user configure it?

from graphql-client.

That's the safest option probably, although  I don't see a use-case for prefixing happening often anymore, since, if my memory is right, we already prefix the generated items with the query name, in addition to wrapping everything in a module. For example:

query People {
  person(id: 1) { name }
}

Will generate a struct called RustPeoplePerson. Fragments are also their own "roots". So collisions can happen but should be rare, so we could probably do custom prefixing, defaulting to nothing.

Example query that should collide with the generated ResponseData without prefixing, for testing purposes:

query Response {
  data
}

from graphql-client.

I was thinking, does ResponseData even need to be generated? Would it make sense to have another struct you annotate with #[derive(GraphQLResponse)like GraphQLQuery? Does that buy us anything?

from graphql-client.

Hmm, sorry for reacting to your last comment that late. Since a given ResponseData's fields are specific to one query, I don't think there is a way around generating it. I am not sure I understand entirely.

from graphql-client.