import syntax in schema

[vektah]

Follow the conventions in https://github.com/graphcool/graphql-import to stitch together multiple schemas.

Prereq for Schema Stitching

[piotrkochan]

this is a must!

[codyleyhan]

Is there potential of doing an even easier solution by just having the user supply a list of files related to the schema in the config file ie:

schema.graphql

type Schema {
   getUser(id: Int) User
}

user.graphql

type User {
 ...
}

gengql.yml

...
schema_files:
    - "schema.graphql"
    - "user.graphql"
...

Which could then be read in and parsed/validated at the same time using the parser? This seems to be pretty easy to implement if it is a good alternative solution

[piotrkochan]

You can write bash or bat script to concatenate these files before gqlgen W dniu pt., 7.09.2018 o 07:24 Cody Ley-Han <notifications@github.com> napisał(a):

…

Is there potential of doing an even easier solution by just having the user supply a list of files related to the schema in the config file ie: *schema.graphql* type Schema { getUser(id: Int) User } *user.graphql* type User { ... } *gengql.yml* ...schema_files: - "schema.graphql" - "user.graphql" ... Which could then be read in and parsed/validated at the same time using the parser? This seems to be pretty easy to implement if it is a good alternative solution — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFXy-XBNKGZNYPOrFFzxiei6eHASPdZqks5uYgLwgaJpZM4SGAX9> .

[rolimb]

Personally, I use simple bash script for it.

./scripts/genSchema.sh

#!/bin/sh
find ../schema -type f -name '*.gql' | xargs -I{} sh -c "cat {}; echo ''" > ../schema/schema_gen.graphql

It simply concatenates all *.gql files under ../schema into single ../schema/schema_gen.graphql file.

Then I just added go:generate above gqlgen:

//go:generate sh ../scripts/genSchema.sh
//go:generate gorunpkg github.com/99designs/gqlgen

Does the job.

[piotrkochan]

Hey @rolimb, you said:

Then I just added go:generate above gqlgen:

Could you clarify where exactly you've added that snippet?

[blasterpistol]

@rolimb can be simplified
for f in ./gql-schema/*.gql; do cat $f; echo; done > ./schema.gql

[rolimb]

@piotrkochan, Not sure about your question. Actually I took your advise:

You can write bash or bat script to concatenate these files before gqlgen

And that's exactly what I did.
Anyway, my resolver.go file looks like this:

// Package graph ...
//go:generate sh ../scripts/genSchema.sh
//go:generate gorunpkg github.com/99designs/gqlgen
package graph

// Resolver ...
type Resolver struct {
	Server *Server
}

// RootMutation resolver
func (r Resolver) RootMutation() RootMutationResolver {
	return r.Server
}

// RootQuery resolver
func (r Resolver) RootQuery() RootQueryResolver {
	return r.Server
}

[rolimb]

@DenisNeustroev, I'm sure it can be simplified and/or done in other million different ways.
But I have to disagree. Yours is limited to a single directory, but I needed to go down the directory tree and pluck all the gql files.

[piotrkochan]

I mean, I haven't seen golang syntax like:

// Package graph ...
//go:generate sh ../scripts/genSchema.sh
//go:generate gorunpkg github.com/99designs/gqlgen

Does it really run these scripts automatically?

[rolimb]

@piotrkochan, I followed the instructions from Finishing touches.
But to make sure it does work, I just deleted all generated files, ran:

go generate ./...

in the project's root and the files got regenerated:

• schema_gen.graphql by 1st statement
• generated.go & models_gen.go by 2nd.

[andrewmunro]

@vektah Is there any updates on this? Looking at the parser this should be possible now? I might have a go at making a PR...

[rodcorsi]

The graphql-import has capability to import one specific element and his dependencies. I think this resource is very useful.

# import createTodo from "schemas.graphql"

Maybe we can reach the same capability in gqlgen.yml

schema:
  - "{createTodo} from schemas.graphql"

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.