# Praxis Table Authoring Settings

> Use when Codex must work on @praxisui/table authoring, Settings Panel integration, config editors, columns editor, behavior editor, filter settings editor, toolbar actions editor, rules editor, CRUD integration editor, value mapping, visual formula builder, JSON config editor, apply/save/reset, or runtime/editor round-trip.

- Skill: `codexrodrigues/praxis-table-authoring-settings` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add codexrodrigues/praxis-table-authoring-settings`
- Raw SKILL.md: https://api.skillmd.com/api/skills/codexrodrigues/praxis-table-authoring-settings/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: codexrodrigues (https://skillmd.com/u/codexrodrigues)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/codexrodrigues/praxis-table-authoring-settings

---


# Praxis Table Authoring Settings

For configuring an installed table inside Page Builder, read
[browser-table-widget.md](references/browser-table-widget.md). Pair it with
`praxis-table-filter-actions` for query ownership and `praxis-ui-product-design`
for composition with other widget types.

Use this skill for table authoring and Settings Panel flows. A table change is incomplete when runtime config works but the visual editor cannot show, edit, apply, save, reset, reopen, or round-trip the same semantics.

## Source Audit

Inspect the real authoring surface:

- `projects/praxis-table/AGENTS.md`
- `projects/praxis-table/src/lib/praxis-table-config-editor.ts`
- `projects/praxis-table/src/lib/praxis-table-config-editor.html`
- `projects/praxis-table/src/lib/praxis-table-widget-config-editor.ts`
- `projects/praxis-table/src/lib/table-editor-document.model.ts`
- `projects/praxis-table/src/lib/table-editor-capability.ts`
- `projects/praxis-table/src/lib/columns-config-editor/**`
- `projects/praxis-table/src/lib/behavior-config-editor/**`
- `projects/praxis-table/src/lib/detail/**`
- `projects/praxis-table/src/lib/filter-settings/**`
- `projects/praxis-table/src/lib/toolbar-actions-editor/**`
- `projects/praxis-table/src/lib/rules-editor/**`
- `projects/praxis-table/src/lib/crud-integration-editor/**`
- `projects/praxis-table/src/lib/value-mapping-editor/**`
- `projects/praxis-table/src/lib/visual-formula-builder/**`
- `projects/praxis-table/src/lib/json-config-editor/**`
- `projects/praxis-table/src/lib/i18n/table-editor.i18n.ts`
- `projects/praxis-table/docs/table-authoring-document-completeness-checklist.md`
- `projects/praxis-table/docs/visual-rules-editor-transition.md`

Also inspect `projects/praxis-settings-panel/AGENTS.md` and the Settings Panel bridge when the change touches `SettingsValueProvider`, drawer data, `apply`, `save`, `reset`, or persisted config.

## Authoring Rules

- Keep the canonical pair `runtime/config <-> editor` in sync.
- Test sparse host configurations and compare the entire persisted document after a single-field edit. Editor defaults must remain transient for untouched settings; action label edits must not author export, row-action or layout defaults. Reuse the Table internal initial/edited projection merge (`table-authoring-changes.ts`) rather than replacing complete config groups. Preserve coupled semantics when explicitly selected, such as hybrid row-action behavior.
- `PraxisTableConfigEditor` implements `SettingsValueProvider`; preserve `isDirty$`, `isValid$`, `isBusy$`, `getSettingsValue`, and apply/save/reset behavior.
- Capture the active columns draft before tab navigation or `getSettingsValue()`/`onSave()` produces a payload, independently of typing debounce; prove immediate edit-to-JSON and Apply/Save without sleeps or debounce ticks, and keep inactive child state from overwriting manual JSON.
- Treat `resourcePath`, `idField`, schema hash, local-data mode, and CRUD context as governed authoring state. Do not silently drop them when normalizing config.
- For columns, always validate runtime rendering, editor visibility, order, type/format, renderer, computed expressions, value mapping, conditional styles, sticky state, and headers.
- Preserve the Core threshold vocabulary in micro-visualization authoring: finite `min`/`max` ranges, progressive `value` cutoffs and discrete `equals` conditions. Presence matters: `equals: 0`, `false` and strings are valid. Range controls must not invalidate or convert existing cutoff/equality documents when editing tone, label or order. Inspect `presentation-visualization.model.ts` normalization and tone resolution; prove primary and conditional-renderer Apply/reopen, retained conditions/labels, cutoff preview, and empty/inverted/non-finite-only negatives in the columns editor specs. Do not require every threshold to have `min` or `max`.
- For `stackedBar`, expose the supported denominator (`total`/`totalExpr`) in ordinary and conditional guided authoring alongside the segment source. An absent total means the category sum; it cannot represent a deliberately partial allocation. Load colored segments and expressions, edit an unrelated property, Apply/Save and reopen; compare the complete document, including unknown authored fields and compose items, rather than checking only the edited field.
- Prove micro-visualization previews through the actual columns-editor DOM after Angular sanitization. Assert proportional widths, zero geometry and category colors, effective `table-cell` context even for omitted/conflicting source surfaces, and application locale. A helper-string assertion does not prove a rendered preview. Reuse Core's structured materialization and the owning renderer's safe boundary; never solve lost styles by trusting arbitrary authored HTML. Inspect `columns-config-editor-renderer-phase2.spec.ts` and compose/conditional paths, and keep failing authoring gates open until the runtime/editor correction is independently verified.
- For filters, keep `behavior.filtering.advancedFilters.settings` synchronized with `FilterSettingsComponent`.
- For rules and formulas, preserve the rule compiler/operator registry and do not reintroduce prohibited old Visual Builder dependencies.
- For actions, preserve global action validation and effect shapes.
- Treat sample-row paths in detail previews as untrusted authored data, including columns, conditions and expression fields. Validate every segment before creating any prefix; reject `__proto__`, `prototype` and `constructor` consistently with Core expression evaluation. Traverse only own properties and create own data properties so inherited objects or setters cannot be mutated. Prove hostile root/nested paths, an inherited object, valid nested paths, zero/false samples, and unchanged source config/no emission in the detail editor spec. Preview generation must not mutate shared prototypes or persisted documents.
- For `surface.open` actions, combine mounted child raw-draft validity with Table document and
  main JSON validation. Invalid-only text must count as dirty, block Apply/Save, survive tab changes,
  and clear only through explicit Reset/Cancel. Track the mounted editor, not label/index identity,
  and prevent removal or replacement that would silently discard the draft.
- Project runtime action availability out of authoring before cloning, normalizing or diffing action arrays. Use the Table owner’s `table-action-authoring-projection.ts` for toolbar, row, bulk and nested children; do not strip arbitrary business payloads or patch only the Page Builder adapter.
- Capture the host-authored `disabled` state before availability overrides it. A later allowed capability must not erase an explicit host denial, and a session denial must not become an authored restriction after a label/order edit. Internal `__praxis*` provenance is runtime bookkeeping, never a public setting or persisted action field.
- For older snapshots without recoverable origin, preserve `disabled: true` and diagnose the ambiguity. Never infer origin from labels, array positions, duplicate identifiers or assumed credentials. Test clean/legacy input, explicit false/true/absent disabled, nested menus, reorder and save/reopen through the real editor.
- For i18n, put editor chrome text in `table-editor.i18n.ts`; do not add visible hardcoded text.
- Keep contextual detail in the canonical `behavior.detail` group. `behavior.expansion` owns row interaction; it must not become a second source for detail source, schema, height, or presentation.
- Give detail a dedicated editor section that covers placement, dynamic or fixed height, empty behavior, source and fallback, the selected-record document, and advanced JSON without losing supported extension properties.
- Delegate selected-record callouts, cards, icons, formatted text, context bindings, and contextual action references to the canonical Rich Content editor. Do not recreate Rich Content appearance fields inside Table.
- Distinguish the selected-record document from shell states. Zero, multiple, off-page, loading, blocked, and error states remain localized Table messages unless the runtime contract explicitly supports rich state documents.
- `emptyBehavior=hide` must remove the panel geometry when no eligible selected record or renderable content exists. `emptyBehavior=message` must expose a useful localized instruction. Missing height defaults to dynamic; fixed height requires a positive pixel value and an internal overflow strategy.
- Rich Content action references must resolve to declared table row actions. The editor may configure the reference and presentation, but it must not invent or authorize a domain action.

Column visibility, reorder, resize, auto-fit, density, and other runtime
customizations must serialize through one persistence lane. Queue/coalesce
overlapping mutations deliberately, acknowledge success, and handle 409/412 by
loading the remote document and reconciling only the changed semantic field.
Never blindly retry a stale whole document or report persisted before the
storage acknowledgement.

## Round-Trip Checklist

For governed page children, inspect `table-page-widget-adapter.ts` and its specs
against Config's `page-publication-p0` profile. Use `decodeTablePageInputs` and
`encodeTablePageInputs` for the native envelope, preserving presence of
`resourcePath` and `horizontalScroll`. Keep config content only in
`definition.inputs.config`; do not pass a fictitious runtime `authoringDocument`.
The initial admitted profile uses compact schema columns (`columns: []`,
`columnProjection.source: 'schema'`) and rejects null anywhere in config.

Project intentional editor changes through `projectTablePageEditorChanges` using
the original raw inputs and the mounted editor baseline/current values. Reuse
the owner delta helper so materialized columns and defaults do not become new
authorship. Fixed bindings require a new widget key and server-admitted seed when
changed. Cover reserved JSON keys, raw presence, schema-column compaction,
Unicode lengths, diagnostics as widget-relative JSON Pointers and the native
Config corpus, then combine the owner validator with the Core page codec.

Materialize execution-only inputs through `materializeTablePageRuntimeInputs`:
Core-derived identity and volatile persistence are runtime projections, never
saved authoring. Check every projected input against both component reflection
and public metadata so the strict Core loader can mount it. Do not copy Form-only
inputs into Table: Table uses `enableCustomization: false` to suppress independent
authoring; it does not declare `showAiAssistant`. Verify filter persistence and
Reset as well as the table key;
a successful editor round-trip alone does not prove storage isolation. Verify in
the runtime that volatile config uses native defaults and explicit
inputs without personal global table/schema/timezone overlays, including after
global changes and Reset. Host tenant/cache/locale/CSP infrastructure remains;
shared global-service reads are not proof that personal table config was applied.
Validate the real mounted advanced-filter child and every projection slot when
testing its persistence flag; an absent child cannot prove isolation. Pair with
`praxis-core-composition-runtime` and the Form round-trip skill for shared page
integration. Page Builder/host publication remains a separate downstream proof.

For every editable field, prove or inspect:

1. Existing config opens in the editor with the correct value.
2. The user can change it through the canonical editor surface.
3. Apply/save emits the expected config/document shape.
4. Runtime reflects the applied change.
5. Reopening the editor preserves the value.
6. Reset does not erase unrelated table state.

Exercise parent config replacement and Reset while the columns editor remains
mounted. Verify the new input replaces the appropriate draft and reconciles the
selection; then edit another property and prove that the emitted document does
not resurrect pre-reset columns, renderers or segment colors. Recreating the child
before checking Reset cannot prove this lifecycle path.

For contextual detail, repeat the proof with no selection, one eligible visible selection, multiple selection, a selection outside the visible page, empty content, resource failure, dynamic height, fixed height, collapse/reopen, and narrow Settings Panel navigation.

Also switch from visual controls to JSON without closing the editor: an untouched
JSON projection must follow current visual edits. Preserve unapplied manual JSON,
including invalid or empty text, instead of overwriting it on input changes. After
the host acknowledges an applied JSON draft, subsequent visual edits must sync
again. Compare the complete document so unknown authored keys are not silently lost.

If no visual editor is affected, say so explicitly and explain why.

## Validation

- Config editor or Settings Panel: `config-editors-integration.spec.ts`, `open-table-settings.spec.ts`, and focused editor specs.
- Columns: `columns-config-editor*.spec.ts` and renderer-specific specs when output changes.
- Filters: `filter-settings*.spec.ts` plus filter E2E when browser interaction matters.
- Rules/formulas: `table-rules-editor*.spec.ts`, `rule-compiler.service.spec.ts`, `visual-formula-builder*.spec.ts`, and `npm run verify:no-visual-builder` when relevant.
- CRUD integration: `crud-integration-editor` coverage plus config editor integration.
- Visual authoring: Playwrights such as `table-json-authoring`, `table-json-rules`, `table-rules-editor`, `column-drag`, and expansion authoring.
- Contextual detail: focused `detail/*.spec.ts`, `praxis-table.bottom-detail.spec.ts`, config-editor initialization/round-trip specs, and `/table-bottom-detail-lab` Playwright coverage for collection chrome, sizing, hidden geometry, Rich Content, and governed actions.

## Companion Skills

- Use `praxis-angular-accessibility-governance` for keyboard resize/reorder, focus, and live persistence feedback.

- Use `praxis-authoring-editors` for cross-component editor, persistence, Settings Panel, and round-trip principles.
- Use `praxis-table-data-source-precedence` for authoring `resourcePath`, local-data mode, bindings, apply-plan diagnostics, and source precedence.
- Use `praxis-table-selection-export-runtime` when Settings Panel authors export, bulk actions, row actions, or selection-dependent behavior.
- Use `praxis-table-renderer-state-diagnostics` when editors change renderer config, formatting, state copy, or visible diagnostics.
- Use `praxis-table-runtime-data` for broader runtime behavior that the editor materializes.
- Use `praxis-table-filter-actions` for filters, actions, CRUD action wiring, and export operation authoring.
- Use `praxis-table-ai-validation` for AI component edit plan coverage and registry ingestion.
- Use `praxis-table-rule-effects-runtime`, `praxis-table-rule-animation-presets`, and `praxis-table-rule-table-integration` when the table rules editor embeds `@praxisui/table-rule-builder` effects, presets, animations, or renderer placement.
- Use `praxis-table-rule-ai-validation` when table visual rule effects are AI-authorable or delegated from the table assistant.
- Use `praxis-ui-product-design` for editor layout, density, accessibility, and screenshot validation.

