Search: order results newest first in every group
Chat hits sort by the chat's last use whatever field matched, and run, step, field, artifact and pipeline hits sort by their own date, before the result cap applies so the cap drops the oldest. Each kind's row scan also walks newest first. Score still reports the match tier. The app sorts both groups newest first as well.
This commit is contained in:
@@ -82,10 +82,10 @@ type SearchRequest struct {
|
||||
Limit int `json:"limit,omitempty"`
|
||||
}
|
||||
|
||||
// SearchResponse is the ranked, bounded set of matches. Results are ordered by
|
||||
// score, then recency, then a stable kind/target tie-break.
|
||||
// For kind-only browsing, order is recency descending, numeric entity/visit IDs
|
||||
// descending, then target ascending, without a text-relevance score.
|
||||
// SearchResponse is the bounded set of matches. Results are ordered by recency
|
||||
// descending (a chat's last use for kind chat), numeric entity/visit IDs
|
||||
// descending, then target ascending, before the cap applies; Score records the
|
||||
// match tier. Kind-only browsing carries no text-relevance score.
|
||||
// Truncated reports that either the result cap or the field-scan budget dropped matches;
|
||||
// ScannedSteps/ScannedBytes and ScanBoundBytes make the body-scan bound
|
||||
// observable.
|
||||
|
||||
Reference in New Issue
Block a user