Sorting of search results

[seelchen]

Description

This PR adds the ability to sort the search results in the SearchView. For this, a button was added to the SearchView which opens a dialog similar to the one for sorting directories.

Additionally, to address issue #3357, this PR adds an option to sort the search results by relevance. This sorting is as described in this comment and is only available for sorting search results and not for directories.

To fully resolve issue #3357, the "old" search has to be embedded in the same search view as the new search view.
However, to avoid bloating this PR, I think it might be better to fix that separately.

Issue tracker

Addresses #3357

Automatic tests

• Added test cases

Manual tests

• Done

Device:

• Pixel 7 emulator running Android 13
• HTC U11 life running Android 10

Build tasks success

Successfully running following tasks on local:

• ./gradlew assembledebug
• ./gradlew spotlessCheck

[seelchen]

This is ready for review!

[VishalNehra]

Works great! One thing I think can be improved, from my initial test is, say if I have files such as
image (1).jpg
image (2).jpg
Some random image name.jpg
It actually matches the last one in relevance ascending. I feel the percentage of match is more in first 2 than the last one.
Here's an example

Record_2023-12-07-02-19-49.mp4

[seelchen]

Works great! One thing I think can be improved, from my initial test is, say if I have files such as image (1).jpg image (2).jpg Some random image name.jpg It actually matches the last one in relevance ascending. I feel the percentage of match is more in first 2 than the last one.

In my understanding, ascending in sort by relevance should sort them from least to most relevant (since for example ascending in sort by size would be from small to large). I also think it's quite confusing, but logically it should be the correct order. Do you think inverting it would be more intuitive?

[VishalNehra]

Yea, descending relevance means least relevant at top and vice versa. I didn't notice this wasn't the original intention.

[seelchen]

Alright, then I will invert it 👍 (although I don't quite understand the logic)

[seelchen]

I pushed a commit to reverse the order - but could you maybe explain again why ascending relevance is from most to least relevant? I still don't quite get it.
If we see relevance as a numeric value, in my opinion less relevant items would have a smaller number and more relevant a larger number. Following this logic, since ascending is from small to large, it would be from least to most relevant.

[VishalNehra]

It's for the UX, just like you said, it'll be confusing for the user. Not all people using the app are technical, they won't see the relevance as a numerical from less to more. Let's try this way, if we get complaints from user that this behaviour is unexpected, we'll revert to your original implementation.