fix(chase): switching the rules invalidates every resolved verdict

The frontend caches statuses and only asks about unknown keys, so flipping
the chase mode left half the screen judged under the old rules until a
restart — which read as the mode not working. The backend now broadcasts an
invalidation and the panels re-ask as rows repaint. The entity badges also
say their name with a question mark, dashed, when the need is only a missing
QSL — the 50% opacity was invisible on a filled chip.
This commit is contained in:
2026-08-30 21:37:31 +02:00
parent 7c10517bf5
commit e4028f4bcd
3 changed files with 16 additions and 3 deletions
+3 -2
View File
@@ -1151,8 +1151,9 @@ export function DecodesPanel({ decodes, txMsgs, txState, txStates, spotStatus, o
{entities.map((b) => (
<span key={b.label}
title={e?.unconf_status ? t('dec.unconfTip') : undefined}
className={cn('rounded px-1 py-px text-[10px] font-bold uppercase tracking-wide shrink-0', b.cls, e?.unconf_status && 'opacity-50')}>
{t(b.label)}
className={cn('rounded px-1 py-px text-[10px] font-bold uppercase tracking-wide shrink-0', b.cls,
e?.unconf_status && 'opacity-60 border border-dashed border-current bg-transparent')}>
{t(b.label)}{e?.unconf_status ? '?' : ''}
</span>
))}
{extras.map((b) => {