Add search relevance criteria to DBT search function #113
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.
Problem
In the DBT search function, search results are sorted in alphabetical order by the model name. This is not optimal for a search function, and can cause some difficulty for visibility of relevant search results for the user.
Solution
To solve this issue, this PR adds a "weight" criteria to each search result, which is an indication of how relevant it is to the user (the larger the number, the more relevant). To specify, weight will be added to a search result if the search query matches the name, tags, description, SQL code, or columns, whose weights are biggest to smallest in that respective order. Based on this, the order of the search results is sorted from the greatest to least "weight," and therefore allows for easier visibility of more relevant search results for the user.
Other Information