-
Notifications
You must be signed in to change notification settings - Fork 54
WhereInput Interface missing for multi level relations #280
Comments
Same issue, and for a TS neophyte like me, a show stopper. |
I've got the same issue as well, for now my solution was to manually copy paste the interface declaration, but of course when I run graphqlgen next time I'll need to do it again.. |
Hey everyone, #267 should normally fix the problem and will land very soon with the next release 🙏 |
Thanks @Weakky ! In the interim, do you have a work around suggestion for a huge Prisma schema? I'm unable to spin up the server. Thanks for any suggestions! (I'm new to Typescript, and thus far. can't figure out why I'm still using it) |
Downgrade graphqlgen until it's working. 😉 |
@sapkra the older versions don't properly scaffold nested resolvers. Probably time to build out in JS and return when the project matures. |
if downgraded to 0.2.7 it kind of works for me :-) |
This is a dealbreaker for us too, would be great to have a release with this feature fixed. Our deeply nested model goes kaBOOM. Thanks for the great work. |
Hey 👋, This should now be fixed by [email protected]. Could you please confirm? Thanks! |
I had the same issue and it fixed it for me 👍 |
Description
I have a User which owns a Calendar and the Calendar has Entries.
CalendarEntryWhereInput
is defined inUserResolvers
&CalendarResolvers
but it's missing in theCalendarEntryResolver
.It has to be in there because the
CalendarEntry
has a relation to the owning User.Maybe one solution is to move these interfaces to a global scope so that all Resolvers are able to use the same interfaces.
Actual results
Cannot compile because an error is thrown.
Cannot find name 'CalendarEntryWhereInput'
Versions
The text was updated successfully, but these errors were encountered: