Armando Pérez Marqués

Same here: - Ubuntu 18.04 - Gnome 3 on X11 - Default window backend (which I assume is Glutin). It could be something specific to the window backend, because if...

Maybe a tag like `@gqlSchema.description = "some string..."` could be added to one of those query/mutation/subscription types to address #33.

hmmmm, inspired from your example, mine could also be: ```ts /** * @gqlType * @gqlOperation query */ export class MyOddlyNamedQueryType { /** @gqlField */ me(): string { return new 'yo';...

Re verbosity: IMO that is not a problem in practice, because defining the `schema` is something done _once_ and most likely it won't ever change. Verbosity could become a problem...

> However that still doesn't give a clear way to add a description to the schema itself True, I forgot about that. This then clearly makes your proposal the way...

(Still tinkering on this) Had to use module remapping to force Grats to use the same (newer) Typescript version used in Deno (v5.2.2 at this time) to be able to...

The problem specific to Deno is just the version used. I think after v5, TS got smarter about module resolution, which might explain why Grats works with this Deno codebase,...

IMO it's the only type-safe solution, since Grats can't/won't alter how `graphql-js` handles this case?