Praxis Table Renderer State Diagnostics
Use this skill when a table issue is about what the user sees: cells, renderers, formatting, empty/loading/error states, diagnostics, or runtime observations.
Rendering is a materialization of table config, schema metadata, rich-content contracts, and runtime state. Do not solve display issues by scraping DOM text or adding one-off host rendering branches.
Source Audit
Inspect before editing:
projects/praxis-table/AGENTS.md
projects/praxis-table/src/lib/praxis-table.ts
projects/praxis-table/src/lib/praxis-table.html
projects/praxis-table/src/lib/praxis-table.scss
projects/praxis-table/src/lib/data-formatter/**
projects/praxis-table/src/lib/utils/rich-content-adapter.ts
- renderer-specific
praxis-table.*rich-content.spec.ts
projects/praxis-table/src/lib/i18n/table-runtime.i18n.ts
projects/praxis-table/src/lib/praxis-table.metadata.ts
- runtime observation and loading state specs when applicable.
Inspect @praxisui/core rich-content, i18n, loading, and runtime observation contracts when those are the shared source.
Renderer Rules
- Resolve renderer behavior from column config, schema metadata, rich-content adapter, and table rule integration. Do not infer renderer intent from labels as the primary decision.
- Preserve renderer-specific contracts for icon, image, badge, link, button, chip, progress, avatar, toggle, menu, rating, html, compose, and micro-visualization.
- Keep row/column conditional renderer placement owned by table; visual effect payload semantics belong to
@praxisui/table-rule-builder.
- Use data formatter services for dates, numbers, booleans, currency, percentage, value mapping, masks, and text transforms.
- Keep unsafe HTML, raw media URLs, large payloads, and unredacted runtime observations out of user-facing diagnostics unless the contract explicitly allows them.
State And Diagnostics Rules
- Loading state should flow through table runtime state and
loadingStateChange, plus shared core loading renderer when configured.
- Empty states should distinguish initial empty, filtered empty, and configured no-data actions.
- Error states should preserve user-visible message, runtime logs, and recoverable action where available.
- Runtime observations must be serializable and redacted, using core observation contracts rather than console-only diagnostics.
- User-facing chrome text belongs in
table-runtime.i18n.ts; editor chrome belongs in table-editor.i18n.ts.
Publish localized live status for resize/reorder/export/filter/persistence
outcomes without duplicate announcements. In strict CSP style mode, disable
runtime operations that require disallowed inline styles and emit a bounded
diagnostic; do not partially execute them.
Aderence Inventory
Classify before adding renderer/state fields:
ja-suportado-so-ux: renderer/state exists but copy, visual affordance, or diagnostics are incomplete.
ja-suportado-mal-nomeado-ou-mal-materializado: a local renderer alias should map to existing column/rich-content/formatter contracts.
suportado-parcialmente: renderer/state works but i18n, accessibility, observation, docs, or focused specs are incomplete.
lacuna-real-de-contrato: no table/core renderer, state, formatter, observation, or rich-content contract can express the visual decision.
Only real gaps justify new public rendering contracts. Otherwise fix materialization, i18n, or diagnostics in the owner.
Validation
Use focused proof:
- matching
praxis-table.*rich-content.spec.ts
data-formatting.service.spec.ts
praxis-table.empty-state.spec.ts
- loading/error/runtime operation specs.
- runtime observation specs when diagnostics are emitted.
- browser screenshot validation for visual, layout, accessibility, or interaction changes.
For first-step issue resolution, audit: source column/schema config, renderer choice, formatter path, rich-content payload, loading/empty/error branch, i18n key, observation envelope, and focused spec coverage.
Companion Skills
Use praxis-angular-accessibility-governance for keyboard, ARIA, focus, live-region, contrast, and reflow proof.
Use praxis-table-runtime-data for surrounding data/pagination/sorting runtime.
Use praxis-rich-content-runtime for rich-content document and node contracts.
Use praxis-table-rule-table-integration for conditional visual effects embedded in table.
Use praxis-core-widget-observations for runtime observation envelopes.
Use praxis-ui-product-design for visual QA.
1---2name: praxis-table-renderer-state-diagnostics3description: "Use when Codex must implement, audit, or debug @praxisui/table renderers and user-visible states: column renderers, rich-content adapters, data formatting, empty/loading/error states, loadingStateChange, runtime observations, diagnostics, i18n copy, row/column renderer precedence, or renderer-specific specs."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-table-renderer-state-diagnostics6---78# Praxis Table Renderer State Diagnostics910Use this skill when a table issue is about what the user sees: cells, renderers, formatting, empty/loading/error states, diagnostics, or runtime observations.1112Rendering is a materialization of table config, schema metadata, rich-content contracts, and runtime state. Do not solve display issues by scraping DOM text or adding one-off host rendering branches.1314## Source Audit1516Inspect before editing:1718- `projects/praxis-table/AGENTS.md`19- `projects/praxis-table/src/lib/praxis-table.ts`20- `projects/praxis-table/src/lib/praxis-table.html`21- `projects/praxis-table/src/lib/praxis-table.scss`22- `projects/praxis-table/src/lib/data-formatter/**`23- `projects/praxis-table/src/lib/utils/rich-content-adapter.ts`24- renderer-specific `praxis-table.*rich-content.spec.ts`25- `projects/praxis-table/src/lib/i18n/table-runtime.i18n.ts`26- `projects/praxis-table/src/lib/praxis-table.metadata.ts`27- runtime observation and loading state specs when applicable.2829Inspect `@praxisui/core` rich-content, i18n, loading, and runtime observation contracts when those are the shared source.3031## Renderer Rules3233- Resolve renderer behavior from column config, schema metadata, rich-content adapter, and table rule integration. Do not infer renderer intent from labels as the primary decision.34- Preserve renderer-specific contracts for icon, image, badge, link, button, chip, progress, avatar, toggle, menu, rating, html, compose, and micro-visualization.35- Keep row/column conditional renderer placement owned by table; visual effect payload semantics belong to `@praxisui/table-rule-builder`.36- Use data formatter services for dates, numbers, booleans, currency, percentage, value mapping, masks, and text transforms.37- Keep unsafe HTML, raw media URLs, large payloads, and unredacted runtime observations out of user-facing diagnostics unless the contract explicitly allows them.3839## State And Diagnostics Rules4041- Loading state should flow through table runtime state and `loadingStateChange`, plus shared core loading renderer when configured.42- Empty states should distinguish initial empty, filtered empty, and configured no-data actions.43- Error states should preserve user-visible message, runtime logs, and recoverable action where available.44- Runtime observations must be serializable and redacted, using core observation contracts rather than console-only diagnostics.45- User-facing chrome text belongs in `table-runtime.i18n.ts`; editor chrome belongs in `table-editor.i18n.ts`.4647Publish localized live status for resize/reorder/export/filter/persistence48outcomes without duplicate announcements. In strict CSP style mode, disable49runtime operations that require disallowed inline styles and emit a bounded50diagnostic; do not partially execute them.5152## Aderence Inventory5354Classify before adding renderer/state fields:5556- `ja-suportado-so-ux`: renderer/state exists but copy, visual affordance, or diagnostics are incomplete.57- `ja-suportado-mal-nomeado-ou-mal-materializado`: a local renderer alias should map to existing column/rich-content/formatter contracts.58- `suportado-parcialmente`: renderer/state works but i18n, accessibility, observation, docs, or focused specs are incomplete.59- `lacuna-real-de-contrato`: no table/core renderer, state, formatter, observation, or rich-content contract can express the visual decision.6061Only real gaps justify new public rendering contracts. Otherwise fix materialization, i18n, or diagnostics in the owner.6263## Validation6465Use focused proof:6667- matching `praxis-table.*rich-content.spec.ts`68- `data-formatting.service.spec.ts`69- `praxis-table.empty-state.spec.ts`70- loading/error/runtime operation specs.71- runtime observation specs when diagnostics are emitted.72- browser screenshot validation for visual, layout, accessibility, or interaction changes.7374For first-step issue resolution, audit: source column/schema config, renderer choice, formatter path, rich-content payload, loading/empty/error branch, i18n key, observation envelope, and focused spec coverage.7576## Companion Skills7778- Use `praxis-angular-accessibility-governance` for keyboard, ARIA, focus, live-region, contrast, and reflow proof.7980- Use `praxis-table-runtime-data` for surrounding data/pagination/sorting runtime.81- Use `praxis-rich-content-runtime` for rich-content document and node contracts.82- Use `praxis-table-rule-table-integration` for conditional visual effects embedded in table.83- Use `praxis-core-widget-observations` for runtime observation envelopes.84- Use `praxis-ui-product-design` for visual QA.