-
Notifications
You must be signed in to change notification settings - Fork 81
Refactor: use hapi joi for validation #33
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
Refactor: use hapi joi for validation #33
Conversation
@erezrokah @theburningmonk |
@horike37 sorry, will take a look today |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@erezrokah
Looks good to me from my perspective 👍
I'm working on DynamDB proxy feature, so I need to reflect this validation logic to my working branch for consistency.
Let me know if you have any questions on migrating to |
@erezrokah Impressive work! It looks good for me too, my one feedback is that it'll be nice to split the |
Thanks for the feedback. |
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixes #27
Joi
errors messages since they were not very useful (see the helpercustomErrorBuilder
function)request
(mapping template) andpartitionKey
async/await
usageaddCors
utility method to avoid code duplication (the one at thes3
package had a better implementation that didn't override existing response parameters)