{{ message }}
Add multi-field search#653
Merged
Merged
Conversation
baev
requested changes
May 15, 2026
Member
There was a problem hiding this comment.
this one should be used last, I would say the order is
"id",
"name",
"fullName",
"owner",
"labels",
"links",
"categories",
"statusMessage",
"historyId",
baev
approved these changes
May 19, 2026
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
2 participants
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 a dedicated search payload for Awesome reports and switches the tree query search to MiniSearch. Search now works beyond test name/id and can match fields like fullName, historyId, owner and visible labels, categories, top-level error messages, and links.
The search data is written separately as widgets/search-index.json and per environment as widgets//search-index.json, so tree.json stays focused on rendering the tree and multi-environment reports only search within the selected environment. The frontend loads and builds the MiniSearch index lazily when a query is entered, then intersects search matches with existing status/tag/category filters.