Move mapping beside database status
This commit is contained in:
@@ -54,7 +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.
|
||||
- Mapping status and mapping source details belong beside the database connection status at the bottom of the sidebar. Style it as a shared sidebar section header with icon, centered status and a fixed right chevron; keep the existing mapping behavior.
|
||||
|
||||
## TypeScript workflow
|
||||
|
||||
|
||||
Reference in New Issue
Block a user