You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README_schema_editor.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,10 +129,26 @@ The Schema Editor lets you copy one or more rows from any tab into a different s
129
129
- Right-click **within the highlighted selection** to preserve the multi-row selection while opening the context menu.
130
130
3. Right-click the selection and choose **Copy to schema**.
131
131
4. In the dialog that appears:
132
-
- Choose the **target schema** from the drop-down list. The schema(s) the selected rows belong to are shown as disabled and cannot be chosen as a target.
133
-
- Review the **Dependencies** list, if shown. Any structural items that must accompany the selection (see below) are listed here.
132
+
- Choose the **target schema** from the **Copy to schema**drop-down. The source schema(s) are shown as disabled and cannot be chosen as a target.
133
+
- Review the three optional sections described below.
134
134
5. Click **Copy**. The rows are appended to the appropriate tabs of the target schema, and a confirmation message reports how many rows were written.
135
135
136
+
#### Dialog sections
137
+
138
+
**Section 1 — Selected rows and their parents (always copied)**
139
+
This section is always visible. The selected rows are listed first, grouped under their tab name. Below them, any structural items they depend on that are not yet present in the target schema (e.g. a Table row that a Field refers to, or a base slot that a slot_usage customises) are listed. Everything in this section is always copied and cannot be individually deselected.
140
+
141
+
**Section 2 — Dependent table records (optional)**
142
+
Child records that belong to the selected rows — for example, Field rows that belong to a selected Table, or Enum value rows that belong to a selected Enum — are listed here. Uncheck the section to skip copying them entirely.
143
+
144
+
**Section 3 — Copy picklists and picklist choices (optional)**
145
+
Enumerations (picklists) referenced by the `range` attribute of selected or subordinate fields are listed here. Each enumeration has its own checkbox; expanding an enumeration shows a checkbox for each individual permissible value. All items are checked by default.
146
+
147
+
- Uncheck an **enumeration** to skip that entire picklist and all its values.
148
+
- Uncheck individual **permissible value** rows to copy the enumeration but exclude specific choices.
149
+
150
+
> **Note:** If you choose not to copy a picklist that one or more fields reference in their `range`, those fields will show a validation error on the Field tab (broken enumeration reference). This is expected — you can resolve it later by either copying the missing picklist separately or updating the field's `range` to point to a picklist that already exists in the target schema.
151
+
136
152
### What gets copied automatically (dependencies)
137
153
138
154
Before appending the selected rows, the editor checks whether any structural items they reference are already present in the target schema. Items that are missing are copied along automatically:
Copy file name to clipboardExpand all lines: lib/DataHarmonizer.js
+23Lines changed: 23 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -218,6 +218,7 @@ class DataHarmonizer {
218
218
copyPaste: true,
219
219
outsideClickDeselects: false,// for maintaining selection between tabs
220
220
manualColumnResize: true,
221
+
manualRowResize: false,// Note Handsontable has a bug according to Claude: What's happening: When the context menu opens (right-click), the ManualRowResize plugin's _onContextMenu handler tries to clean up its resize-guide DOM element by calling parent.removeChild(element). But a HOT re-render (triggered by, e.g., hidden-rows plugin recalculating, or switching selection across a tab with many rows) has already detached and re-created that DOM node, so the parent no longer holds the original node reference — causing the NotFoundError.
221
222
//colWidths: [100], //Just fixes first column width
0 commit comments