If a category has exact name entered, show it first

[nicolas-raoul]

WIth the latest Git, yesterday I got this situation: I typed the name of a category that I know exists, but I had a hard time finding it, because it was far down in the suggestions.

My suggestion: If a category has exact name entered (ignoring uppercase/lowercase), show it first

[misaochan]

Agreed, that would be good!

[ismailisimba]

You could design the search method to check for similarities ignoring caps, then by simple calculation decide if by how much percentage the query matches a category. Then sort the results from highest match to lowest.

[nicolas-raoul]

@ismailisimba Something similar has already been implemented by @misaochan, please see https://github.com/commons-app/apps-android-commons/wiki/Category-suggestions-%28readme%29
Cheers!

[Kartikdot]

Is the issue still open? if yes, can i work on it ?

[misaochan]

@Kartik2016 Please feel free, thanks! :)

[pszklarska]

If @Kartik2016 doesn't work on this issue, I'd like to fix this :)

[nicolas-raoul]

Oh, sorry for not assigning this one in time...
It seems that both @Kartik2016 and @pszklarska started working on it at the same time. Apologies for the confusion, this time I guess it makes sense to assign it to @pszklarska who has sent a pull request already. In the future we will try to assign sooner!

[nicolas-raoul]

Hum, looks like Github does not allow me to assign to anybody outside the organization, actually!
This means we need another way to indicate that an issue is assigned... maybe a label?
In any case we will need to make that explicit in the documentation.

[misaochan]

Yeah, the assignment is messy. :/ Maybe we could just state in comments "assigned to [name]", along with adding that label?

[nicolas-raoul]

Strangely I still see this problem recently, the category with the entered name is very far in the list of suggestions:

[gupta-meghna64]

@nicolas-raoul This is strangely weird. I tried with exactly the ones you tried, and they're appearing at the top of list for me :-/

[nicolas-raoul]

@gupta-meghna64 I am using the Play Store beta version, I guess this has been fixed in master? :-)

[gupta-meghna64]

Yes @nicolas-raoul :)

[nicolas-raoul]

Happening currently in 2.8-release branch: