You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional context If downgrade only the @graphql-mesh/runtime to version 0.43.4 in the above package, all of the mentioned errors will not occur. All other conditions are the same.
The text was updated successfully, but these errors were encountered:
uknowpro
changed the title
Error: Cannot return null for non-nullable field (source from graphql handler)
Error: Cannot return null for non-nullable field when using multiple source handler
Nov 28, 2022
uknowpro
changed the title
Error: Cannot return null for non-nullable field when using multiple source handler
Error: Cannot return null for non-nullable field when using multiple source handlers
Nov 28, 2022
if do not use bare merger, this response error occurs in both graphql source and openapi source. "TypeError: Cannot read properties of undefined (reading 'Query')"
transform is applied to the openapi source, there is no error. (sure graphql source)
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
[CASE 1] Use merger: bare And multiple source handler(graphql, openapi) in mesh config
[CASE 2] Un-use merger: bare And multiple source handler(graphql, openapi) in mesh config
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When using graphql and openapi handlers, I want the query to work by applying transforming normally without errors.
Environment:
@graphql-mesh/...
:"@graphql-mesh/cli": "^0.80.1",
"@graphql-mesh/config": "^8.0.34",
"@graphql-mesh/graphql": "^0.32.2",
"@graphql-mesh/merger-bare": "^0.15.49",
"@graphql-mesh/openapi": "^0.33.38",
"@graphql-mesh/runtime": "^0.44.35",
"@graphql-mesh/transform-filter-schema": "^0.14.112",
"@graphql-mesh/transform-naming-convention": "^0.12.2",
"@graphql-mesh/transform-rename": "^0.13.1",
"@graphql-mesh/transform-resolvers-composition": "^0.12.110"
Additional context
If downgrade only the @graphql-mesh/runtime to version 0.43.4 in the above package, all of the mentioned errors will not occur. All other conditions are the same.
The text was updated successfully, but these errors were encountered: