graphql-let

graphql-let copied to clipboard

API design of Resolver Types feature is problematic/misleading

8

When using the Resolver Types feature it is adding the output to all files including the document types. One of the features of Resolver Types is the ability to use...

marklawlor

Problem when using next's getServerSideProps

3

Hey, thanks for this project, we're having a great time using this with next, but while everything is fine with getStaticProps or when working local, it doesn't work with getServerSideProps...

gsimone

How to import enum from graphql schema to resolvers

4

Using next.js example https://github.com/vercel/next.js/tree/canary/examples/with-typescript-graphql when I try to do the following: ```graphql # lib/type-defs.graphqls type Query { viewer: User! } # introduced Test enum enum Test { VALUE_1 VALUE_2 }...

michalkvasnicak

Support writing configuration as webpack Loader option

5

From https://github.com/piglovesyou/graphql-let/pull/78#issue-401108869 > Ideally it should also be available as a Webpack Loader option. The problem is the command-line execution, but maybe we can get it from `webpack.config.ts`. Reasonable spec...

piglovesyou

* https://github.com/YousefED/typescript-json-schema to get JSON schema from `src/lib/config.ts` * Validate when graphql-let loads a user config by https://github.com/tdegrunt/jsonschema This will avoid pitfalls of typos and non-supported options to be specified.

piglovesyou

piglovesyou

**Problem** There's some NPM vulnerabilities in packages this one uses (i.e. babel stuff). It's a little more burdensome to the consumer of this package to update if the versions aren't...

comp615

I'm currently trying to generate typesscript types via CLI, but no type files a getting created. My queries are stored in .ts files and look like this for example: My...

hendrik244

Absolute imports in graphql files

1

Feature request: Support absolute paths in imports. Allow this: ```# import 'lib/fragments/FoobarFields.graphql'``` In place of this: ```# import '../../../../lib/fragments/FoobarFields.graphql'``` Particularly helpful since my editor does not autocomplete path nodes in...

timscott

Hello, As `graphql-let` is not actively maintains anymore, I think a disclaimer should be add at the start of the README file. Two years ago I add the opportunity to...

kornfleks