# Praxis Table Runtime Data

> Praxis Table Runtime Data

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

---


# Praxis Table Runtime Data

Use this skill for the `@praxisui/table` runtime surface. The table is the canonical Angular runtime for enterprise table materialization, but it is not the primary source of backend semantics. Backend resource semantics come from `praxis-metadata-starter`; governed configuration and publication belong to `praxis-config-starter`; shared Angular models and services often belong to `@praxisui/core`.

## Source Audit

Inspect the real source before changing table runtime behavior:

- `projects/praxis-table/AGENTS.md`
- `projects/praxis-table/src/public-api.ts`
- `projects/praxis-table/src/lib/praxis-table.ts`
- `projects/praxis-table/src/lib/praxis-table.metadata.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/local-data/**`
- `projects/praxis-table/src/lib/data-formatter/**`
- `projects/praxis-table/src/lib/analytics/**`
- `projects/praxis-table/src/lib/detail/**`
- `projects/praxis-table/src/lib/components/praxis-analytical-drawer/**`
- `projects/praxis-table/docs/local-data-mode-precedence.md`
- `projects/praxis-table/docs/resource-events.md`

Also inspect `projects/praxis-core/src/lib/models/**`, `services/**`, and `src/public-api.ts` when the behavior depends on `TableConfig`, `GenericCrudService`, `ResourceDiscoveryService`, `RestApiLinks`, `PraxisCollectionExportService`, loading, logging, i18n, global actions, surfaces, capabilities, analytics, or runtime observations.

## Canonical Runtime Rules

Honor the official data-source precedence:

1. Explicit `resourcePath` from input, quick connect, or `document.bindings.resourcePath` wins.
2. Local `data` array activates local mode only when no explicit `resourcePath` exists.
3. Persisted connection is fallback only when neither explicit `resourcePath` nor local mode applies.

Treat `resourcePath + data` as remote mode. Clearing `document.bindings.resourcePath` is the explicit authoring path for removing a remote connection.

Do not add a local adapter, fallback, or special host branch when `GenericCrudService`, `/schemas/filtered`, `_links`, capabilities, resource surfaces, or table config already governs the operation.

## Platform Aderence Inventory

Before adding a runtime input, config field, event, service, renderer, export option, analytics shape, or public API, classify the need:

- `ja-suportado-so-ux`: the runtime has the state/operation and only needs better materialization.
- `ja-suportado-mal-nomeado-ou-mal-materializado`: the contract exists but the table labels, mapping, or defaults obscure it.
- `suportado-parcialmente`: table has part of the behavior but needs owner-aligned extension.
- `lacuna-real-de-contrato`: no canonical source can provide the data or behavior.

Only `lacuna-real-de-contrato` can justify a new public contract. Prefer fixing `@praxisui/core` for shared models/services and `praxis-metadata-starter` for backend metadata semantics.

## Runtime Change Guidance

- For remote resource flows, ground columns, filters, id fields, actions, surfaces, and availability in schema/capability discovery instead of hardcoded host lists.
- Keep persisted-config hydration distinct from input changes. During the initial storage merge, retain a valid saved `actions.bulk.position` over a discovery default while refreshing the host's action contracts and selection. In `ngOnChanges`, an earlier input is not a persisted preference: the current explicit bulk position must win over that earlier position. Omission does not imply reset. Do not change the shared initial-merge precedence or invent a host flag to correct input ordering.
- After asynchronous persisted config hydration, materialize the existing defaults, feature guards and derived columns coherently before notifying Angular with `markForCheck`, and before awaiting unrelated widget inputs. A notification alone can remove NG0100 while leaving `displayedColumns` stale. Do not hide that inconsistency with timers, forced `detectChanges`, changed getters or suppressed errors; reuse the Table-owned projection path.
- For analytical-drawer metadata, let Core `ResourceDiscoveryService` resolve root-relative discovery URLs against the configured API origin; do not append `/schemas/**` to the CRUD `/api` base or change the host API base to compensate. Query the exact governed collection operation in `/schemas/catalog`, require one matching path/method, and follow its published `schemaLinks.response`. A resource path is not a semantic resource key: never replace slashes with dots to guess one. Surface-catalog operation descriptors are not drawer layouts; preserve explicit input/DI layouts and consume only the already-supported explicit layout extension when the returned structural schema contains it. Missing/ambiguous metadata leaves the remote layout absent. The removed beta `surfaceName` input must not be restored as a parallel discovery mode.
- Invalidate drawer metadata and relation reads on resource/context change, resource removal, and destroy, including authority changes for the same user and tenant. Cancel obsolete requests, guard late callbacks, clear retained relations and old layout/cache state, and preserve method plus resolved URL in relation-cache identity. A metadata epoch alone cannot prevent redisplaying a cached authorization snapshot.
- For local data mode, keep behavior contained in `src/lib/local-data/**` and preserve the documented precedence.
- For data formatting, renderers, rich content, rating, badges, links, chips, progress, avatar, media, compose, and micro-visualization, verify the renderer contract and the rich-content adapter before changing table chrome.
- For export, use `PraxisCollectionExportService` and declared export config; do not invent direct CSV/PDF generation inside a host.
- For analytics, use `analytics-table` models/services and core analytics projection contracts instead of bespoke dashboard payloads.
- For runtime observations, use the core observation registry rather than console-only diagnostics.
- Reuse `behavior.detail` for both row and bottom placement. Bottom detail consumes exactly one eligible visible selected row; preserve the configured multiple-selection policy and never silently select the first record.
- Keep collection chrome structurally connected. `presentation.bottomStackPosition=afterControls` is the default enterprise order after the footer toolbar and paginator; use `beforeControls` only as an explicit product decision. A hidden or empty detail surface must not leave margins, borders, fixed height, or an empty flex/grid track.
- Missing detail height means dynamic sizing. Fixed height requires a positive pixel value and scrolling inside the detail body so the paginator and footer remain reachable.
- Treat detail resource responses as untrusted documents. A Table `resourceAllowList` only restricts the canonical same-origin pathname; it does not authorize records, fields, methods, redirects, or tenant access. Propagate the canonical request context, enforce authorization at the backend endpoint/resolver, fail closed on non-2xx responses, and protect corporate endpoints with timeout and response-size policies.
- Invalidate selected-record detail on tenant/context change, row replacement, page visibility loss, and newer data/detail responses. A matching record id across two tenants is not the same authorization context.
- For public or untrusted hosts, consume the Table-owned runtime profiles. A
  profile must close the input shape and declare every possible resource-read
  operation, including compatibility fallbacks. `effects: []` means local-only;
  it is not permission to execute arbitrary config. Resolve profiles through
  the Core service and keep capability/authorization enforcement separate.

## Validation

Prefer the smallest reliable validation:

- local data or precedence: `local-data/*.spec.ts` plus affected `praxis-table.*.spec.ts`
- remote resource regression: `praxis-table.remote-regression.spec.ts` or a focused runtime spec
- bulk-position hydration: persistence-merge cases plus real CRUD/Table lifecycle with capabilities-first and saved-config-first arrival, toolbar/both/no-saved-config controls, current actions/selection and no forced change detection hiding missing notifications. Verify the browser flow with its error checks intact; a preference regression test alone does not prove resolution of a separate Angular check-cycle error.
- async selection hydration: exercise the real host/CRUD/Table without bulk actions, independently release the host and Table reads of the same saved config in both orders, and hold widget-input hydration pending. Assert selection, `displayedColumns`, rendered checkbox and `checkNoChanges` before and after releasing inputs, retaining the ErrorHandler. Unit acceptance does not replace a browser check on rebuilt packages.
- analytical-drawer discovery: its component spec for root/base-relative hrefs, API prefixes, exact catalog queries, absent/ambiguous schema, cancellation and same-principal context changes; then a direct-host browser proof that waits for metadata/data readiness and records failed URLs before asserting an empty console. Public GET evidence proves the backend query, not patched browser adoption.
- renderers/rich content: the matching `praxis-table.*rich-content.spec.ts`
- export/global action/runtime operation: focused runtime spec plus AI/runtime operation spec when assistant behavior is involved
- public API/exported contract: `npm run build:praxis-table` plus a direct consumer or adapter validation when applicable
- runtime profile: metadata/profile specs plus
  `ComponentRuntimeProfileService` happy, mismatch, and adversarial shape proof
- browser-visible behavior: focal Playwright under `projects/praxis-table/test-dev/e2e/**`
- contextual bottom detail: selection/state specs plus `/table-bottom-detail-lab` Playwright proof for paginator/footer adjacency, before/after control ordering, zero geometry when hidden, dynamic/fixed height, collapse focus, late responses, and narrow layout

When PowerShell is unavailable, run equivalent local manifest/frontmatter/hash checks for skill changes and state the limitation.

## Companion Skills

- Use `praxis-table-data-source-precedence` for focused local/remote data-source resolution, `resourcePath`, `queryContext`, persisted connections, local pipeline, and apply-plan diagnostics.
- Use `praxis-table-selection-export-runtime` for selected rows/ids, `selectionChange`, bulk state, export scopes, and collection export requests.
- Use `praxis-table-analytics-stats-runtime` for analytic-table projections, stats request execution, fallback rows, and dashboard table views.
- Use `praxis-table-renderer-state-diagnostics` for renderers, rich-content cells, formatting, empty/loading/error states, i18n, and runtime observations.
- Use `praxis-table-filter-actions` for filters, toolbar actions, row actions, bulk actions, filter drawer adapter, global actions, and action grounding.
- Use `praxis-table-authoring-settings` for Settings Panel, config editors, round-trip, resourcePath, idField, and editor parity.
- Use `praxis-table-ai-validation` for table AI manifest, component edit plans, runtime operations, context packs, registry ingestion, and AI E2E.
- Use `praxis-core-resource-runtime` for schemas, actions, surfaces, capabilities, HATEOAS, option sources, CRUD operation resolution, and resource discovery.
- Use `praxis-ui-product-design` for visual table UX and screenshot validation.

