feat: treat unhandled exceptions in handlers as 500 error responses #1642
Annotations
4 errors and 2 warnings
test/node/rest-api/response/throw-response.node.test.ts > throws non-Response errors as-is:
test/node/rest-api/response/throw-response.node.test.ts#L109
TypeError: Cannot read properties of null (reading 'name')
❯ test/node/rest-api/response/throw-response.node.test.ts:109:23
|
test/node/msw-api/setup-server/scenarios/on-unhandled-request/callback-throws.node.test.ts > prevents a request when a custom callback throws an exception:
test/node/msw-api/setup-server/scenarios/on-unhandled-request/callback-throws.node.test.ts#L42
AssertionError: expected 'Must not resolve' to be 'Failed to fetch' // Object.is equality
- Expected
+ Received
- Failed to fetch
+ Must not resolve
❯ test/node/msw-api/setup-server/scenarios/on-unhandled-request/callback-throws.node.test.ts:42:32
|
test/node/msw-api/setup-server/scenarios/on-unhandled-request/error.node.test.ts > errors on unhandled request when using the "error" value:
test/node/msw-api/setup-server/scenarios/on-unhandled-request/error.node.test.ts#L70
AssertionError: expected 'Must not resolve' to be 'Failed to fetch' // Object.is equality
- Expected
+ Received
- Failed to fetch
+ Must not resolve
❯ test/node/msw-api/setup-server/scenarios/on-unhandled-request/error.node.test.ts:70:32
|
build
Process completed with exit code 1.
|
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, pnpm/action-setup@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build
No files were found with the provided path: test/browser/test-results. No artifacts will be uploaded.
|