suessflorian / gqlfetch

Generates a graphql server schema using introspection.

Hi

NZ based software engineer studying for a Masters in CS @ The University of Auckland. I carry quite a bit of interest in Go, with particular focus on projects such as bramble, graph-gophers, genqlient, gqlgen, right now. Currently learning a little more about PostgresQL, with particular focus on extensions like pg_trgm, postgres_fdw and pg_roaringbitmap.

Other interests include; tackling scalability problems, debating software architectures, recommender systems via matrix factorization, using nvim, (py)spark alternatives like dask.

I like to document my learnings in the forms of small problem-centric projects, please check them out!

• Use case of FOREIGN DATA in Postgres
• Logical Postgres Replication
• Tackling scalable process management

You'll see me hanging out on math stack exchange and stack overflow occasionally too.

gqlfetch's Issues

BUG, Extra square brackets

Additional square brackets

• [WorkPartition]! -> [[[WorkPartition]!]]!
• ID! -> [ID]!

However non-required fields are ok

Package should not have unresolved panics

Currently package can panic on http client request posting or decoding schema response.

Double quotes in comments cause errors

If a field comment ends with double quotes, it causes issues.

type {
"""Comment with "double quotes""""
  id: ID
}

This was automatically generated fetching a public schema.
I believe we need to use """ as proper multi-lines to make this work

error: No query string was present

Hi there,

I keep getting this error from the server and upon further inspection this happens because the query operation type is being sent as uppercase Query

{"Query":"query IntrospectionQuery {\n __schema {\n...

Server returns

{
  "errors": [
    {
      "message": "No query string was present"
    }
  ]
}

the query works fine if operation type is sent as: query

{"query":"query IntrospectionQuery {\n __schema {\n...

---

I'll be happy to submit a PR if needed, but it is such a minor change might just be easier for you guys to commit the change.

I couldn't find anything on wether the spec requires this to be uppercase or lowercase but from my experience I have always seen the operation types being sent lowercase. They are also shown lowercased in the spec.

Missing support for new default directive specifiedBy

Recently there were added specifiedBy directive, which is supported by new versions of gqlgen and gqlparser. We need to add to excludeDirectives list for gqlfetch to work properly with this new standard.

Built in types and directives

At this moment gqlfetch prints all types and directives fetched from a server. Problem is that build in types and directives are also printed which conflicts with genclient when I tried to generate code with error like

invalid schema file ./schema.graphql: Cannot redeclare type Float.

Interface arguments are not generated

Description

If an interface field has arguments, they will not be generated. This causes errors when using the exported schema in genqlient.

Steps to reproduce

1. Create a new go project

   $ mkdir sample-gengqlient-project
   $ cd sample-genqlient-project
   $ go mod init sample-genqlient-project

2. Run go install github.com/suessflorian/gqlfetch/gqlfetch@latest
3. Run gqlfetch --endpoint https://gitlab.com/api/graphql > schema.graphql
4. Run go run github.com/Khan/genqlient@latest --init and observe that the it is unable to init the project because of the interface and implementation argument mismatch.

What license is this project released under?

Description

I'm looking at using this project, but I'm unable to do so at the moment without a software license. Is the project intended to be used under a specific license?

From the GitHub docs.

You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.

Empty inputs

Hey @suessflorian, thanks for the tool.

I fetched schema and found that all inputs are empty, no fields specified

input UpdateWorkTemplateInput {
}

If I want to use schema for genqlient I need inputs, so genclient can generate proper code.