We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Progress of the issue based on the Contributor Workflow
Make sure to fork this template and run yarn generate in the terminal. Please make sure Mesh package versions under package.json matches yours.
Make sure to fork this template and run yarn generate in the terminal.
yarn generate
Please make sure Mesh package versions under package.json matches yours.
package.json
Describe the bug
When defining responseByStatusCode with schema for 404 responses, it misses it and throw.
responseByStatusCode
To Reproduce Steps to reproduce the behavior:
Set config
responseByStatusCode: 200: responseSchema: ./src/schemas.json#/definitions/goodResponse 400: responseSchema: ./src/schemas.json#/definitions/errorResponse 404: responseSchema: ./src/schemas.json#/definitions/errorResponse
200 and 400 works fine, 404 throws error:
GraphQLError: HTTP Error: 404, Could not invoke operation GET /api/ at Object.createGraphQLError (./node_modules/@graphql-tools/utils/cjs/errors.js:9:12) at field.resolve (./@omnigraph/json-schema/index.js:664:40) at processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 0) at async promiseForObject (./node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:14:28) at async ./node_modules/@graphql-tools/batch-execute/cjs/createBatchingExecutor.js:44:36 at async Promise.all (index 0) at async DataLoader.batchExecuteLoadFn [as _batchLoadFn] (./node_modules/@graphql-tools/batch-execute/cjs/createBatchingExecutor.js:42:25) { path: [ 'getExpense' ], locations: undefined, extensions: { http: { status: 404, statusText: 'Not Found', headers: {} }, request: { url: 'https://api', method: 'GET' }, responseJson: { errorCode: 404, errorMessage: 'error message' } } }
Expected behavior
To recognize this response :)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
When defining
responseByStatusCode
with schema for 404 responses, it misses it and throw.To Reproduce
Steps to reproduce the behavior:
Set config
200 and 400 works fine, 404 throws error:
Expected behavior
To recognize this response :)
The text was updated successfully, but these errors were encountered: