feat(chase): the switches follow the operator, not the panel
Chase POTA, US counties, prefixes and grids were written for the cluster and stayed there, so an operator who does not chase parks still met NEW POTA in the FT decode list and in Chase new: the same badge withdrawn on one screen and shouting on the next. The setting is about what is hunted. One helper answers the question for every panel, keyed by both the status field names and the shorter category names so a single call serves badges and filter chips alike. Chase new also stops CATEGORISING a row by a marker that is switched off, which had left rows listed with no visible reason for being there. A new US state has no switch of its own, so it is always allowed.
This commit is contained in:
@@ -44,6 +44,27 @@ export function chaseGrid(): boolean {
|
||||
try { return localStorage.getItem('opslog.chaseGrids') !== '0'; } catch { return true; }
|
||||
}
|
||||
|
||||
// chaseAllows answers "does this operator chase this kind of thing at all?"
|
||||
// for the ORTHOGONAL markers — park, square, prefix, county.
|
||||
//
|
||||
// The switches were written for the cluster and stayed there, so an operator
|
||||
// who does not chase parks still met NEW POTA in the decode list and in Chase
|
||||
// new: the same badge, withdrawn on one screen and shouting on the next. The
|
||||
// setting is about what the operator hunts, not about which panel is open.
|
||||
//
|
||||
// The keys are both the status-entry field names (new_pota…) and the shorter
|
||||
// category names the panels filter with (pota…), so one call serves both.
|
||||
// Anything without a switch of its own — a new US state — is always allowed.
|
||||
export function chaseAllows(key: string): boolean {
|
||||
switch (key) {
|
||||
case 'new_pota': case 'pota': return chasePota();
|
||||
case 'new_grid': case 'grid': return chaseGrid();
|
||||
case 'new_pfx': case 'pfx': return chasePfx();
|
||||
case 'new_county': case 'cty': return chaseCounty();
|
||||
default: return true;
|
||||
}
|
||||
}
|
||||
|
||||
// Both options are withdrawn from the filter panel for now. The machinery below
|
||||
// is deliberately kept whole — it is correct and hard-won — so putting the two
|
||||
// switches back is this one flag and the block they came from in App.tsx.
|
||||
|
||||
Reference in New Issue
Block a user