Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

do not render default resolver when field has no type #474

Merged
merged 1 commit into from Apr 8, 2019

Conversation

Projects
None yet
2 participants
@koenpunt
Copy link
Contributor

koenpunt commented Apr 8, 2019

Not sure in which scenario this happens, but it does happen that getType() returns undefined, causing generation to fail.
By ensuring the type is not undefined, generation works fine.

do not render default resolver when field has no type
Not sure in which scenario this happens, but it does happen that `getType()` returns undefined, causing generation to fail.
By ensuring the type is not undefined, generation works fine.

@jasonkuhrt jasonkuhrt merged commit b6632eb into prisma:master Apr 8, 2019

1 check passed

deploy/netlify Deploy preview ready!
Details

@koenpunt koenpunt deleted the koenpunt:patch-1 branch Apr 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.