-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Closed
Description
Search first
- I searched and no similar issues were found
What Happened?
This is pretty BIG ISSUE. As far as I thinking about search in terms «it could be very slow, but find what I need», but not in terms «sometimes it cannot find page» — I even don't know how much times I thought «there is no such note in my graph» instead of real «the app couldn't find it».
NOTE: this doesn't related to graph size
Reproduce the Bug
- Create a reference to the page with name: «this is the page and its name is very long — so long, that final words cannot be found in logseq search and this is a REALLY big issue»
- Open search (cmdk) & try to find by search term «really iss»
- See, there is no such page in search results, but there is the result in blocks section
NOTE: the first words of the page name easily could be found:
Expected Behavior
- All pages would be found despite of length of the name.
- What I expect from the search, is that the relevance would be increasing with entering the characters. That means every new character in search input would decrease the number of found pages. The current state is different:
Number of search results changes with typing in this demo: 99+ → 99+ → 29 → 8 → 1 → 5 (!) → 0 → 2 (!) → 0
Desktop or Mobile Platform Information
MacOS v13.4
Logseq Desktop v0.10.6
Metadata
Metadata
Assignees
Labels
No labels