Closed rdboyes closed 10 months ago
This is probably my fault. When @drizk1 fixed a bug in the behavior of n()
inside of @slice()
, I messed with some of the grouping mechanics in his code. I fixed one issue but may have missed or caused this one. Should be easy to fix.
Also entirely possible that I introduced this bug as well. I'm happy to take a look at it.
I updated to the development version and this seems to be fixed! Sorry for the fake bug report/thanks for fixing this, depending on whether you updated it recently
The current developmental version should match the latest release version. I think I may have fixed this issue in the last couple of versions when I was going through @drizk1's PR. I'll confirm on my end if it works and will close the issue after I confirm.
Just confirmed that it works correctly.
The slice macro interacts differently with @group_by depending on whether you use positive or negative selection in slice.
Produces the expected result:
While the negative version, which should be equivalent:
Ungroups the data, giving: