-
Notifications
You must be signed in to change notification settings - Fork 38
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
option :async is not passed to http sender #167
option :async is not passed to http sender #167
Conversation
options = { json_api_host: config.json_api_host, logger: config.logger } | ||
options = { | ||
json_api_host: config.json_api_host, | ||
async: config.async, |
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.
can you puts async first so the order is alphabetical (like the SQS sender)?
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.
ok
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.
Don't remember so much the code but would it be easy to add specs to ensure that switch case statement passes the expected options to the correct initializer?
299eff3
to
dd38985
Compare
specs added |
Thanks! |
v0.37.0 said it added an
async
option to the HTTP and SQS senders, but in fact only added to SQS. This PR fix it.