-
Notifications
You must be signed in to change notification settings - Fork 316
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
Fix bulk_update #534
Fix bulk_update #534
Conversation
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 your contribution! Could you please add a test case and a changelog entry for it?
Codecov Report
@@ Coverage Diff @@
## master #534 +/- ##
==========================================
+ Coverage 98.07% 98.07% +<.01%
==========================================
Files 29 29
Lines 883 884 +1
Branches 153 153
==========================================
+ Hits 866 867 +1
Misses 12 12
Partials 5 5
Continue to review full report at Codecov.
|
Yes, of course |
Done |
I should add the record to changelog also |
I also changed the version |
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 so much @satels for the thorough work, I think when you address @Stranger6667 's feedback, this could be well-baked and ready to come out of the oven 🍰
I will make changes tomorrow. |
Ok, this pull request is ready to merge |
Thanks! Could you, please, rebase? I can't do automatic rebase due to conflicts |
I did rebase for that |
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.
Some really well-baked stuff, congrats on the first PR in django-money @satels 🎉
Co-Authored-By: Benjamin Balder Bach <benjaoming@gmail.com>
Guys, is there any eta to release the 1.1 version to pypi? I would really appreciate to have this fix. |
Reviewed the changes and 1.0...master seems fine. Wondering why it got bumped to 1.1 since the current changes don't have anything backwards incompatible or big big features. But I guess it's fine, we can be generous with the version numbers now that we're past 1.0 :) |
@Stranger6667 shall we? |
Let's do it :) |
Cool, pushing some buttons now |
Modeled on django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on #534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on django-money/django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Modeled on django-money/django-money#534, which I see came out of a similar issue as I've been seeing now: "AttributeError: 'Coalesce' object has no attribute 'rhs'
Close #507 and double issue #533