Niklas Ye f75ae60e74 fix: truncate in runes rather than bytes ...

truncate measures and slices by byte, so a string cut inside a
multi-byte rune both mis-measures the fixed-width column it is being
laid out against and emits a broken character. Everything it is handed
is server-supplied — alert names, label values, annotations — and none
of that is guaranteed to be ASCII.

Identical behaviour for the ASCII case.

2026-08-07 13:31:51 +02:00

..

keys.go

feat: Stage 1 scaffold — config, API client, placeholder TUI

2026-05-21 13:28:13 +02:00

model_test.go

test: cover the API client and the update loop

2026-07-31 07:23:43 +02:00

model.go

feat!: stats as a section instead of an overlay

2026-08-06 12:46:38 +02:00

styles.go

feat!: incidents as the primary object

2026-07-30 21:54:54 +02:00

update_test.go

feat!: stats as a section instead of an overlay

2026-08-06 12:46:38 +02:00

update.go

feat!: stats as a section instead of an overlay

2026-08-06 12:46:38 +02:00

view_test.go

feat!: stats as a section instead of an overlay

2026-08-06 12:46:38 +02:00

view.go

fix: truncate in runes rather than bytes

2026-08-07 13:31:51 +02:00