acro5piano's comments

Thank you!

As far as I know, json-schema just checks type in runtime right? I don't know how we let TypeScript check json-schema type in compile-time.

GRelDAL is an interesting project! N+1 problem in GraphQL is difficult problem. It remind me Lighthouse PHP [1] which is a GraphQL framework top of Laravel. Lighthouse handles N+1 problem to create a lot of "union all" queries.

[1] https://github.com/nuwave/lighthouse

Thank you for pointing out. I haven't used such tools, but with editor support we can do furthermore.

Type information can be perfectly inferred from the schema. I agree though.

> I wonder how schema information/introspection from the back end could be used to improve this further.

Yes, Apollo's schema validation is really awesome as we can find wrong type before we run code. I would like to add feature in the future.

Thank you for your suggestion!

> What's the advantage of using this tool instead of apollo-cli/apollo-codegen?

> Unfortunately I'm not yet able see any benefits you'd get over Apollo's codegen in return

> Doesn’t Apollo’s Codegen tool already solve this?

I am sorry for my late response.

I add the section to README.md which explains why I created this library even there is Apollo CLI's codegen.

https://github.com/acro5piano/typed-graphqlify#why-not-use-a...

In short,

- Simplicity make this tool works as expected

- Can handle multiple schemas

- Works without schema file

I wrote a lot there, but I just wanted to try the paradigm TypeScript -> GraphQL conversion, because there are no tools to do that, unlike GraphQL -> TypeScript conversion tools.

However, this is not just a hobby project, cause I use this in my current real world project, and it reduces a lot of boilorplate. So I submit here.

# I thought Apollo codegen needs .graphql extension and webpack loader, but it reads .ts files too... Awesome.