-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
Deep stringify worker options to account for hash in on_conflict #506
Conversation
First of all a massive thank you for both PRs! Secondly, would it be possible to get a test that makes this fail unless the deep stringify keys are present? I'm asking because obviously there was missing test coverage to begin with and I'd like to improve that :) I can also add it after merging if you are in a rush, would be great to have this fixed once and for all. In all honesty, I didn't quite understand the problem initially. |
"lock" => :until_and_while_executing, | ||
"on_conflict" => { | ||
"client" => :log, | ||
"server" => :reschedule, |
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.
Yup! This test should be good enough!
abeb1c1
to
50d0f51
Compare
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.
Nice work!!
No description provided.