generating core failed: unable to load github.com/kelvin/gqlgen-todos/graph/model - make sure you're using an import path to a package that exists

[kelvinink]

What happened?

I encountered an issue when following the init instruction to init my example gqlgen project. When I ran go run github.com/99designs/gqlgen init it output an error message:

Creating gqlgen.yml
Creating graph/schema.graphqls
Creating server.go
Generating...
generating core failed: unable to load github.com/kelvin/gqlgen-todos/graph/model - make sure you're using an import path to a package that exists

Exec "go run ./server.go" to start GraphQL server

What did you expect?

I expect it to generate the models, resolvers. But it didn't.

Minimal graphql.schema and models to reproduce

versions

• gqlgen version?
• v0.15.0
• go version?
• go1.16.3
• dep or go modules?

[yash492]

I'm having the same issue. I think there's something broken in new release (v.15.0).
Try using this version.
go get github.com/99designs/gqlgen@v0.14.0

Worked for me.

[ManWithA1000Names]

If you want to use v0.15.0, you can for now comment out the autobind option in the gqlgen.yml and it should work fine:

# ...
resolver:
# ...
  autobind:
    - "your module name/graph/model"

||
\/

# ...
resolver:
# ...
#  autobind:
#    - "your module name/graph/model"

[ipfans]

Yes, You have some workarounds for this(choose the one you like):

1. comment the autobind section so you will not auto load the empty dir.
2. Touch a new empty go file in graph/model dir:

echo "package model" > graph/model/_tmp_gqlgen_init.go

[StevenACoffman]

Sorry folks! I would appreciate more code coverage around this area, so PRs are welcome.

[domgolonka]

Seems the issue persists, but when I am commenting out autobind, the generate fails to find my custom models:

modelgen: required package was not loaded: gitlab.com/domgolonka/api/scalars.UUIDmake: *** [generate] Error 1

[ipfans]

@domgolonka Hi, have you tried the master branch yet?

[zachsmith1]

@ipfans and @StevenACoffman this is still an issue on 0.16 and on master. I was simply trying out the demo here and it wouldn't work.

Note: there may be different issues. I want to point out that the autogenerated config file by init adds a directory to the autobind section. This makes an immediate call to generate (with no changes) to fail.

Go version: 1.17

[iamjenechka]

what if I use a private code repo?

[StevenACoffman]

@honeywild should be fine!

Also, I think the documentation has been corrected now to comment out the autobind until you actually have files in there to autobind to @zachsmith1