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
fix: Connection config nodetype #352
Conversation
Codecov Report
@@ Coverage Diff @@
## main #352 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 21 21
Lines 745 745
Branches 51 51
=========================================
Hits 745 745
Continue to review full report at Codecov.
|
b9dc4df
to
7f34d22
Compare
@@ -75,7 +75,7 @@ export type ConnectionArguments = { | |||
|
|||
type ConnectionConfig = { | |||
name?: string, | |||
nodeType: GraphQLNamedType | GraphQLNonNull<GraphQLNamedType>, | |||
nodeType: GraphQLOutputType, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saihaj Output types include arrays :( so we can't use it
How about you add GraphQLInputNamedType
and GraphQLOutputNamedType
to graphql-js
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was merged and released to 16.x.x
alpha channel graphql/graphql-js#3063 as we discussed on Slack I will update to use alpha for main
and then I can rebase this branch
Found this bug in TypeScript Migration #340 a6d412e