Jordan Eldredge

I think I was imagining something more like: ```typescript /** * An amazing schema! * @gqlSchema */ type Schema { /** * The query operation * @gqlOperation */ query: Query,...

> hmmmm, inspired from your example, mine could also be: [...] Yeah, I like that a bit better than the version with the dot syntax. However that still doesn't give...

> Module remapping must be done carefully to ensure a single graphql version is pulled, otherwise graphql itself will complain. This is also a problem generally, but maybe easier to...

Would the TS version be fixed if we switched to making TypeScript a peer dependency (with constrained versions?)

In theory when we do applyServerDirectves (or in some similar place) we could wrap the resolver functions to match what the user-defined code expects, but I think that's probably not...

This has been fixed for a while

This seems sensible to me. Feel free to ping me when this diff is ready for review (I see it's still marked as Draft).

I wonder if there's a sensible way to add some tests which assert that the compiler and this code arrive at the same hash?

@cometkim Yeah, I could have sworn we had a workspace setup. Here's where we do the global yarn install. I guess we'll need to either setup the workspace or manually...

Either way. Whatever you prefer.