Replies: 3 comments
-
So I'm actually having this exact same issue. I've tried using relative paths to the package, along with absolutes and I'm still having seeing the issue. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
I suggest that do not use |
Beta Was this translation helpful? Give feedback.
-
I am sure this must be something I am doing wrong. If you have any suggestions on how I can debug or where to look in the generation package, I will investigate further
What happened?
autobind works for many of my explicitly defined models, on the most recent one, it fails
What did you expect?
I expected generation to not generate a model that already exists
Minimal graphql.schema and models to reproduce
I cannot reproduce this. It seems completely random that this particular model didn't work. It represents an input type, but I have other input types bound as well. I am happy to investigate further with some guidance on where to start looking
I also tried directly binding the model in the same way as Timestamp, but the same error occurred
versions
gqlgen version
11go version
? 1.14Beta Was this translation helpful? Give feedback.
All reactions