-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 aggregate group id #5994
Fix aggregate group id #5994
Conversation
@dplewis I will still add a test case. |
@dplewis it should be good now |
Codecov Report
@@ Coverage Diff @@
## master #5994 +/- ##
==========================================
- Coverage 93.68% 93.65% -0.03%
==========================================
Files 156 156
Lines 10926 10926
==========================================
- Hits 10236 10233 -3
- Misses 690 693 +3
Continue to review full report at Codecov.
|
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.
this is funny and could be an advertisement against javascript :).
this solution looks good to me, but is hard to read.
Here's my take at a test that is easier to read:
_.isNil(v) || _.isEmpty(v) && !_.isNumber(v);
here's a test of it: https://runkit.com/arthur/reallyempty
def not asking you to change it, but I just couldn't resist trying to futz with it ;).
I'd be surprised if there isn't a more concise test, but I tried.
It is really weird. What we want to do in that line is actually return null if:
I suspect there is no beautiful way to do this :) Your solution fails for boolean. Se here: https://runkit.com/adavimacedo/5d6ca8163db2fb001a475448 |
* Fix aggregate group id * Improve implementation * Add test case * Fix postgres test - it does not work with group and sort at same time
Close #5989