-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Search bar should prioritise exact file name matches over fuzzy matches #217
Comments
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days. |
I think this is really serious problem. ... I don't see why this issue has been closed as completed.. |
Agreed that this should not be labeled as "completed" -- thanks for flagging this @rightx2 👍 |
Re-categorizing this as a feature request and labeling as "help wanted". |
Related comment I left on the PR: #145 (comment) |
Created a PR for this issue |
Describe the bug
Searching for a model e.g.
f_my_model
often returns results where the model in question is surprisingly far down the list.We often have models with similar names with different underscores, for instance
a_users
andb_users
orf_orders_current
andh_orders_old
(I have had to make up some names here).Steps To Reproduce
Open the generated dbt documentation, and search for a model name in the top bar. Type the exact model name (minus extension), and observe that the model is not always the first hit.
Expected behavior
Exact model name should be listed at the top.
Screenshots and log output
I can't provide any screenshots due to it being a private dbt project, but just to provide explicit context, this is the search field I mean:
The output of
dbt --version
:The text was updated successfully, but these errors were encountered: