Flavian Desverne

Oh yeah, I re-read the issue and saw how it wasn't really clear given my wording. Sorry about that too 🙏 > This is so surprising to me that I...

Hey there, Apologize for the inconvenience, this is a regression that was introduced after the major refactor to support enums. This will be fixed once #284 is merged and released....

Hey @koenpunt, Your issue should now be fixed by [email protected] !

Hey apalm 👋, I can confirm this is a bug as we should at least throw an error if we didn't intend to allow several models with the same name!...

Hey @czystyl ! I suggest you wait a little bit for #244 to be merged before spending too much time implementing ReasonML. #244 implements a simplified AST to abstract most...

## Update (breaking change) We'll follow the same conventions as for flow, almost like you suggested Stephen, but with underscores to replace namespaces. eg: ```ts export const User_defaultResolvers = {...

## Update After discussing with @schickling, here's the syntax we came up with (assuming we're splitting the `graphqlgen.ts` file): Given the following GraphQL schema: ```graphql type User { ... }...

Hey, thanks for the PR! There is indeed an issue here, but that doesn't have to do with the filter. The filter is here to prevent the TS enums from...

No, `/packages/graphqlgen/src/introspection/ts-ast.ts` isn't the right file to modify ! Enums are treated as "scalars", which means we always, always take the enums from your GraphQL schema and "copy/paste" them at...

The `typesMap` is the map of all the model definitions per files, and the `modelMap` is indeed a map of all the model definitions that maps to a graphql type....