Category Selection Incorrectly Matches Substring Instead of Exact Match
in progress
N
Nick Miller
When an LM category is a substring of another, typing in the shorter category does not select it. For example, with the categories "Parents" and "Rent", typing the category "Rent" selects "Parents", when it should select "Rent".
Expected behavior: When typing a category name, the system should select the exact matching category.
Steps to reproduce:
- Have at least two categories where one is a substring of another (e.g., "Rent" and "Parents")
- Begin typing the shorter category name ("Rent")
- Observe that the wrong category ("Parents") is selected
Log In
Jen from Lunch Money
marked this post as
in progress
J
Jonathan Lovelace
This appears to default to the alphabetically-first category that contains what the user has typed as a substring; for the "steps to reproduce" above to illustrate the problem the longer-named category needs to be earlier than the other category in alphabetical order.
Allowing the user to type any substring is in my opinion a valuable feature (in my case, I have several categories "Misc Such-and-such", and it's easier to omit the "Misc" when categorizing a transaction)---but I do think that if any category or categories
start with
what the user types (not just exact matching), it or they should be the first/default result(s).