Replies: 2 comments 4 replies
-
Please share a reproduction with a partial openapi schema so we can debug the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@ardatan Here is a minimal reproduction
Or if you need a full project here is a minimal reproduction project: https://codesandbox.io/s/graphlql-mesh-openapi-bug-1c1tm8 (I'm not quite sure how to make graphql-mesh open in codesandbox though? But you can just clone the files and run it locally and run Once you run it, if you do any valid query, e.g. this:
You'll get a response like this:
Again it includes this |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
I have multiple openAPI rest endpoints I am using in my graphql-mesh. However whenever I query one, they always return this annoying object that I don't think I have any use for? called
_openAPIToGraphQL
.example response:
I really just want the records here, I don't want to waste my users data, or add the complexity of including all this metadata in each request.
I thought the obvious solution was to just add
includeHttpDetails: false
but that doesn't seem to do anything?Here's my graphQL mesh file:
is it a bug that the
includeHttpDetails: false
doesn't do anything? Or am I using it wrong perhaps? Or is there another method to not include all this meta data?Beta Was this translation helpful? Give feedback.
All reactions