Don't silently drop properties when processing an httpRoute
#762
Conversation
bitgopatmcl
changed the title
httpRoute
bitgopatmcl
force-pushed
the
VL-1836-fix-error-message
branch
from
ae0b7ce to
addbc6c
Compare
bitgopatmcl
force-pushed
the
VL-1836-fix-error-message
branch
2 times, most recently
from
92d03a1 to
48821de
Compare
bitgopatmcl
force-pushed
the
VL-1836-fix-error-message
branch
from
48821de to
bc65c5f
Compare
|
🎉 This PR is included in version @api-ts/openapi-generator@3.6.2 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/express-wrapper@1.0.26 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/superagent-wrapper@1.2.1 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/typed-express-router@1.1.6 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/io-ts-http@3.1.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
Fixes an issue where errors are swallowed while processing an
httpRoute. Generally this happens while processing a request type, the error just gets swallowed and therequestproperty is omitted from the resulting schema. This then errors out later on in the section of the codebase that expects a request to be there, causing this hard-to-debug error:With this change, the actual error is passed all the way through, making it much easier to see what went wrong.