-
Notifications
You must be signed in to change notification settings - Fork 348
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
graphql-mesh is unable to properly generate types from openapi yaml file, generates JSON types instead. #3942
Comments
If the type is not a certain object type, it puts an empty JSON type. Please make sure you have a correct schema type in your OpenAPI schema. |
Not sure to understand... could you give an example of something wrong in the yaml file please? |
Hello, I have the exact same issue, as @gablabelle described. |
Currently we are rewriting the OpenAPI handler and releasing it as We cover more cases than the old open api handler. I did more improvements and fixes based on You can test it using canary versions commented in the PR until it gets released and we'd appreciate if you give us a feedback in the meanwhile :) If you have any more issues, feel free to create a new issue with a reproduciton on CodeSandbox or StackBlitz or a failing test PR :) Thank you very much for all those information. |
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
Unable to properly generate types, returns JSON instead.
Maybe there is a problem with the YAML file but it seems to validate OK in online validators.
To Reproduce
Steps to reproduce the behavior:
I have setup a codesandbox here:
https://codesandbox.io/s/staging-lake-ervh5v?file=/swagger.yaml
Expected behavior
Graphql-mesh should generate the proper type.
Environment:
Packages
"@graphql-mesh/cli": "0.70.3",
"@graphql-mesh/openapi": "0.25.6",
"@graphql-mesh/transform-resolvers-composition": "0.12.53",
"graphql": "16.0.1",
"graphql-fields": "2.0.3"
Many thanks for your time and help.
The text was updated successfully, but these errors were encountered: