-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trim down prefixing of generated items #80
Comments
Should we do no prefix by default and let the user configure it? |
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 Example query that should collide with the generated query Response {
data
} |
I was thinking, does ResponseData even need to be generated? Would it make sense to have another struct you annotate with |
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. |
Remove the "Rust" prefix from generated items (closes #80)
We don't need the
Rust
prefix, probablyThe text was updated successfully, but these errors were encountered: