Should search on category screen show all children of matching parents?

[spencerkoo]

• When searching categories from Settings -> Data -> Categories
• When you type and you find a result from the "top" or "one of the middle nodes" on a subcategory branch, it does not allow you to expand that node to see which subcategories are under it
• This is particularly useful if you know the general category, but aren't sure if you had any subcategories below that node

[mtotschnig]

* When searching categories from Settings -> Data -> Categories

* When you type and you find a result from the "top" or "one of the middle nodes" on a subcategory branch, it does not allow you to expand that node to see which subcategories are under it

* This is particularly useful if you know the general category, but aren't sure if you had any subcategories below that node

Currently, the logic of the search is to show all nodes that match the search term + their ancestors. Your suggestion would be to show all nodes that match + their ancestors + their descendants. I understand that there are use cases where this is preferable, but I am not 100% sure if it is generally the better strategy.

[spencerkoo]

I understand why the logic you used was initially chosen as you could really manually search through the tree and look -- though that takes a bit more time

My argument for showing descendants is that:

1. You don't need to show any more information than you have currently if you have the descendants toggled closed in the results tree (I don't think that it would slow down the query that much except for extreme cases).
2. But that allows you to cover some more use cases like: if you cannot remember the specific subcategory you made for a not-often used transaction, but you remember the more general category OR if you're cleaning up your category tree, know you have duplicates, and want to see the respective subcategories under those duplicates before merging or changing them