Skip to content

Refactor alert layer visibility handling - #700

Open
Atmosfearful wants to merge 1 commit into
mainfrom
refactor/alert-map-layer-visibility
Open

Atmosfearful wants to merge 1 commit into
mainfrom
refactor/alert-map-layer-visibility

Conversation

@Atmosfearful

@Atmosfearful Atmosfearful commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

Goal

Prerequisite cleanup before #641
Per comment here #641 (comment)
Extract alert map visibility handling while keeping the behavior consistent.

Screenshots

Not applicable; no UI changes.

What I changed and why

Moved alert-group and secondary-data layer visibility into shared helpers. Both the legend toggle and reset now use the same rules, reducing duplicated logic and keeping layer visibility in sync.

How I convinced myself this is right

All 786 unit tests passed, along with the production build and ESLint. I also added tests for alert layers, missing layers, and the secondary-data stroke. An independent review found no remaining issues.

What I'm not doing here

I’m not refactoring the broader map setup or layer creation code.

LLM use disclosure

GPT-6 Luna for discovery, plan, implement, review loop via OpenCode TUI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant