Bus profile normalization makes whitespace-bearing profile keys unselectable #44

Open
opened 2026-10-18 08:57:58 +08:00 by Breadway · 0 comments
Owner

Found during independent PR43 / CRUMB-33 review by comparing src/bread_events.rs:117-121 and Config::profile exact-key lookup against base 7ab4ac23. Confidence: high (source-level; no live bus interaction). Existing behavior introduced by PR41 / 4ddf38a, preserved unchanged by PR43. A configured key such as " home " is allowed by the profile map but a bus set_profile payload is always trimmed to "home", so the exact key cannot be selected. Also whitespace-only string payloads get the misleading diagnostic missing string "profile" rather than empty profile. Decide whether to reject/normalize profile keys consistently or preserve exact-key selection before normalized fallback; add isolated bus-command/config fixtures. Nonblocking for the DNS fix.

Found during independent PR43 / CRUMB-33 review by comparing src/bread_events.rs:117-121 and Config::profile exact-key lookup against base 7ab4ac23. Confidence: high (source-level; no live bus interaction). Existing behavior introduced by PR41 / 4ddf38a, preserved unchanged by PR43. A configured key such as " home " is allowed by the profile map but a bus set_profile payload is always trimmed to "home", so the exact key cannot be selected. Also whitespace-only string payloads get the misleading diagnostic missing string "profile" rather than empty profile. Decide whether to reject/normalize profile keys consistently or preserve exact-key selection before normalized fallback; add isolated bus-command/config fixtures. Nonblocking for the DNS fix.
Sign in to join this conversation.
No labels
bug
ci
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadcrumbs#44
No description provided.