Contacts and Dailer shall search string of numbers encapsulated as floating (*ABC*), using wildcards (or regexp)
- /e/ version: 0.10-2020081367789
- Device model: LG-H850
- Reproducible with the last /e/ version:
- Reproducible with LineageOS:
Summary
Contacts and Dailer do not search a string of numbers using wildcards (e.g. search is foo)
This improvement concerns
-
UI -
Behavior -
Privacy
Description
What is the current behavior?
Consider searching for a contact with phone number ABC DEF GHI
(all digits, spaces independent)
OK results:
- search for
ABC
- the considered contact is offered in search results
Not OK results:
- search for
BCD
orGHI
or anything, if the search phrase is not equal to the start of the telehone number, e.g.ABC
- the considered contact is not offered in results
Search DEF
does not yield results.
Search pattern foo
is equivalent to ^foo
The side effect is that the user has to consider and include also the country codes in search pattern (+12 or 0012) and it does matter, whether the contact's phone has a country code, has a +
or has a 00
starting sequence.
What is the improved behavior?
Search pattern foo
shall be equivalent to *foo*
(wildcards) or .*foo.*
(regex)
Searching for DEF
brings up contacts with ABC DEF GHI
or ADE FBC GHI
What does it bring?
Improved search results.