Feat/indexing UI#1639
Open
Mestane wants to merge 59 commits into
Open
Conversation
…nd description layout
Mestane
force-pushed
the
feat/indexing-ui
branch
from
45f393a to
e605405
Compare
Mestane
force-pushed
the
feat/indexing-ui
branch
from
e605405 to
00b25d1
Compare
Mestane
force-pushed
the
feat/indexing-ui
branch
from
719c915 to
55c6491
Compare
Fall back to the project's fzf over entry titles when the inverted index has no exact or prefix match, so typos still find settings. Index results lead; fzf only fills the gaps.
Mestane
force-pushed
the
feat/indexing-ui
branch
from
55c6491 to
0f141e2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds full-text search to the settings panel. Typing a query shows grouped result cards that deep-link to the matching setting, scrolling to it and flashing it.
The index is generated from the page QML at build time (so it always matches the UI) and baked into the plugin binary as a resource, rather than shipping as a user-editable file. Search runs over an inverted index with prefix matching and relevance ranking, and matched terms are highlighted in the results.
settings search is a hybrid setup a build-time python script parses the page QML and bakes an inverted index (+ ranking weights) into the plugin binary. at runtime it hits that index first (exact + prefix, title weighted over keywords, AND across words), and only falls back to fzf on the titles when the index comes up short, like for typos. index results lead, fzf just fills the gaps.
the python script isn't a rival fuzzy matcher to the shell's fzf util it runs at build time and does zero searching. it just prepares the index. the actual fuzzy matching is the same fzf the launcher uses. different layers: python builds the index, fzf searches it.
There's a developer guide in the README (collapsible section) covering how to add or remove settings from the index.