Skip to content

fix(tabular-editor): disable nested-field parsing#1164

Merged
nicolaskempf57 merged 1 commit into
mainfrom
fix/structured-publishing
Jul 7, 2026
Merged

fix(tabular-editor): disable nested-field parsing#1164
nicolaskempf57 merged 1 commit into
mainfrom
fix/structured-publishing

Conversation

@nicolaskempf57

@nicolaskempf57 nicolaskempf57 commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Replace the watch([tableRef, schemaFields]) + initializeTable() combo with a self-stopping watchEffect that initializes the Tabulator table exactly once.

PapaParse warnings (e.g. ragged rows) are now logged as warning: the parsed data is still loaded into the table. Only the PapaParse error callback or a synchronous exception falls back to an empty table.

Disable Tabulator's nestedFieldSeparator so schema field names containing dots (e.g. note_c2.1) are treated as flat keys.

Without this, Tabulator tries to traverse dotted field names as object paths and can throw "Cannot assign to read only property" when the parent value is a primitive string.

…g watcher, non-fatal PapaParse warnings, and disable nested-field parsing

Replace the watch([tableRef, schemaFields]) + initializeTable() combo with a self-stopping watchEffect that initializes the Tabulator table exactly once.

PapaParse warnings (e.g. ragged rows) are now treated as non-fatal: the parsed data is still loaded into the table and the warnings are logged. Only the PapaParse error callback or a synchronous exception falls back to an empty table.

Disable Tabulator's nestedFieldSeparator so schema field names containing dots (e.g. note_c2.1) are treated as flat keys.

Without this, Tabulator tries to traverse dotted field names as object paths and can throw "Cannot assign to read only property" when the parent value is a primitive string.
@nicolaskempf57
nicolaskempf57 merged commit 50b6afb into main Jul 7, 2026
29 of 31 checks passed
@nicolaskempf57
nicolaskempf57 deleted the fix/structured-publishing branch July 7, 2026 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants