Place mapping status with parser tools

2026-08-05 17:59:51 +02:00
parent 588c0bd9cc
commit c94b514647
2 changed files with 10 additions and 10 deletions
@@ -54,6 +54,7 @@ This project replaces the Excel/VBA workflow named `Catalog maker - 20` with a N
 - Custom select controls may use a native select as an interaction layer, but the native label must be visually transparent when a separate display label is rendered; never show the same control text twice.
 - Runtime button labels must update the existing direct child label span instead of replacing `button.textContent`; state changes must never remove the button icon.
 - Parser tools are always visible in the left panel. Do not hide, collapse or replace the parser action buttons with a toggle; the user must see the complete parser action set at all times.
+- Mapping status and mapping source details belong directly with the parser action group, because mapping is parser output; keep the existing mapping behavior and only change its placement when refining the sidebar.

 ## TypeScript workflow