-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
DDB: parity fix for JS clients #12083
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
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 30m 36s ⏱️ - 1h 22m 45s Results for commit 43743b8. ± Comparison against base commit 5399278. This pull request removes 2840 and adds 1 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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.
The changes look great. I think this will need to be ported to DDB v2 provider too, did you run any checks there?
The behavior was the same. I ported the fix over 👍 |
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.
Thanks for fixing this @giograno !
Motivation
We got a report from a customer mentioning that an empty parameter list in an execute statement command does not raise any error against LocalStack when using the JS client.
For instance, the following snippet would raise a
ValidationException
error against AWS, but not against LocalStack.Changes