-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
stub_responses with Hash vs. Type #1097
Comments
Thank you for reporting the issue and for the excellent reproduction steps. Off the top of my head I'm not sure what the root cause it, but I'll take a look. |
I found the issue and the fix was pretty straight forward. When stubbing response data with a hash, the data is used to generate an HTTP response. There was a bug in how we created the response body for Query based services that used flattened XML maps. The fix should go out with our next release. |
❤️ for fixing this so fast |
Hi,
first of all I have to give you props for the awesome client_stubbing feature. A great way to reliably write test against API mocks.
To my understanding the stub_responses method should not care if passed a Hash or a typed result, eg.
Hash
vsAws::SQS::Types::GetQueueAttributesResult
I prepared a little script to illustrate this. Is this intended?
If you point me to the code where something goes wrong, I'm happy to prepare a PR
The text was updated successfully, but these errors were encountered: