Closed rbyh closed 3 months ago
Can you say a bit more here - what's the expected behavior?
If I sort by column A, and then by column B, I expect column A to remain the first sorted thing (like SQL). But it does the reverse -- it makes column B the first sorted thing.
I see. This might be challenging because it would require the dataset to have a "memory" of what is sorted by and I'd prefer to keep it stateless. What about is sorted could take multiple keys, like this:
results.sort_by('a', 'b')
which would sort by a, then b.
Yes, I would prefer sort_by('a', 'b')
but I thought we discussed a reason to not do it that way?
New version does sort this way - can you update docs, @rbyh ?
I expect it to sort fields in the order that I have applied it, but it does it in reverse: