Trace node search: prefix matches should take priority over substring matches #129

New Issue

2026-10-05T01:58:56+02:00

adam commented

2026-10-05 01:58:56 +02:00

When searching for a node in the trace feature by entering something like 1A, the results include nodes where 1A appears anywhere inside the public key, not just at the start. This drowns out the actually relevant results.

Expected: when searching for 1A, results should be nodes whose name is 1A (or starts with it) or whose public key starts with 1A, in that order.
Actual: any node whose public key contains 1A anywhere in the middle also shows up, making it hard to find the intended node.

When searching for a node in the trace feature by entering something like `1A`, the results include nodes where `1A` appears anywhere inside the public key, not just at the start. This drowns out the actually relevant results. Expected: when searching for `1A`, results should be nodes whose name is `1A` (or starts with it) or whose public key starts with `1A`, in that order. Actual: any node whose public key contains `1A` anywhere in the middle also shows up, making it hard to find the intended node.

adam closed this issue

2026-10-05 01:58:56 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#129