resolvers filename_template not working

[araufdogan]

What happened?

I want to split resolvers by name.

What did you expect?

Split query and mutation resolvers by file name. I have two mutations named login and logout, It should generate two resolvers named login.resolvers.go, logout.resolvers.go. (I deleted the single resolver file before trying to generate it)

gqlgen.yml

schema:
  - graphql/*.graphqls

exec:
  filename: graphql/generated/generated.go
  package: generated

model:
  filename: graphql/model/models_gen.go
  package: model

resolver:
  layout: follow-schema
  dir: graphql
  package: graphql
  filename_template: "{name}.resolvers.go"

Minimal graphql.schema and models to reproduce

type Mutation {
  login: String
  logout: Boolean
}

versions

• gqlgen version? v0.13.0
• go version? go1.14
• dep or go modules? go modules

[ahummel25]

@araufdogan I was trying to do this same thing with my resolvers where they would be split out into their respective files. Are you sure this functionality exists with gqlgen? I never had any luck..

[araufdogan]

@ahummel25 I have no idea. I don't understand how filename_template works. If I need to create a new .graphqls file to using this, we can't split queries or mutations because the same type name allowed only for one file (can't define another query or mutation type in another graphqls file).

Should I create the same resolvers where I want to do and redirect them?

[ahummel25]

I honestly don't know.

I've just been creating my queries and mutations under something like graphql/schema/some_various_files.graphql, running go run github.com/99designs/gqlgen generate (and subsequently letting that command create one monolithic graphql/resolvers/root.resolvers.go file) and then after that, picking out my query and mutation resolver code from that file and manually placing it in new files (user.resolver.go, auth.resolver.go, etc.). My code works fine after doing this, but obviously that's not the correct way to do it. But I simply don't know how to specify otherwise in the gqlgen.yml file and have it work naturally with the generate command.

[diep-it-dn]

Hi, see here if this one helps you!
#1427

[ahummel25]

Hi @diep-it-dn , thanks for that issue link! But it still appears that there is some manual involvement in regards to deleting the originally generated file, right? I guess that's just how it is.

[diep-it-dn]

hi @ahummel25
yes, we have to copy the old function body in the old generated files to the newly generated files based on the new configuration then remove old files.