From 8ee5b31c6205dac5d438ef0a27cd4071b1a312c5 Mon Sep 17 00:00:00 2001
From: "TheDave94 (via AI)" <claude@aliasmailbox.org>
Date: Tue, 19 May 2026 10:39:01 +0000
Subject: [PATCH] feat(editor): derive target_section options from section meta
 map
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The custom-card editor's target_section dropdown was hardcoded to the
five canonical sections (custom_cards/overview/areas/weather/energy).
That meant any new section type (plants, agenda, vacuums, etc.) couldn't
receive a custom card via the editor — users had to hand-edit YAML.

Switch the source of truth to _sectionMeta, the same Map already
populated for the section-order panel. New sections automatically appear
in target_section dropdowns without any further editor changes.
---
 src/editor/StrategyEditor.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/editor/StrategyEditor.ts b/src/editor/StrategyEditor.ts
index 24d3b1f0..d4a08b5f 100644
--- a/src/editor/StrategyEditor.ts
+++ b/src/editor/StrategyEditor.ts
@@ -1744,9 +1744,9 @@ class Simon42DashboardStrategyEditor extends LitElement {
             <label>${localize('editor.target_section')}:</label>
             <select
               @change=${(e: Event) => this._updateCustomCardField(index, 'target_section', (e.target as HTMLSelectElement).value)}>
-              ${(['custom_cards', 'overview', 'areas', 'weather', 'energy'] as const).map((key) => html`
+              ${[...Simon42DashboardStrategyEditor._sectionMeta.entries()].map(([key, meta]) => html`
                 <option value=${key} ?selected=${(card.target_section || 'custom_cards') === key}>
-                  ${localize(Simon42DashboardStrategyEditor._sectionMeta.get(key)!.labelKey)}
+                  ${localize(meta.labelKey)}
                 </option>
               `)}
             </select>