Praxis Metadata Editor Renderer Coverage
Use this skill for visual metadata authoring coverage in @praxisui/metadata-editor. The editor owns the UI that edits canonical FieldMetadata; it does not render final form fields at runtime and it must not duplicate @praxisui/dynamic-fields component semantics.
When locating files, first resolve the Angular workspace root. Paths below are relative to
praxis-ui-angular/projects/praxis-metadata-editor unless another package is explicitly named.
Canonical Boundary
@praxisui/metadata-editor owns:
FieldMetadataEditorComponent
DynamicEditorRendererComponent
ConfigRegistryService
EditorComponentRegistryService
EditorProperty[] config catalogs under src/lib/config/*.config.ts
DynamicFormFactoryService
SchemaNormalizerService
- metadata-editor AI adapter, manifest, context pack, and capability catalog when visual coverage is AI-authorable
- visual coverage docs/checklists
@praxisui/dynamic-fields owns the actual field components, control type discovery, descriptors, and runtime interpretation. When a dynamic-field runtime property is missing from the editor, add visual coverage in metadata-editor; do not copy runtime component logic into the editor.
Required Source Audit
Inspect before editing:
projects/praxis-metadata-editor/AGENTS.md
README.md
docs/metadata-editors-architecture.praxis.md
docs/EDITOR-COVERAGE-CHECKLIST.md
docs/HINTS-STYLE-GUIDE.md
src/public-api.ts
src/lib/components/field-metadata-editor/field-metadata-editor.component.ts
src/lib/components/dynamic-editor-renderer/dynamic-editor-renderer.component.ts
src/lib/config/*.config.ts for the affected control type
src/lib/config/inline-filter-control-properties.map.ts when inline filter coverage is involved
src/lib/config/inline-editor-coverage.spec.ts
src/lib/services/schema-normalizer.service.ts
src/lib/services/dynamic-form-factory.service.ts
src/lib/registry/config-registry.service.ts
src/lib/ai/praxis-metadata-editor-authoring-manifest.ts and spec when the surface is AI-authorable
src/lib/ai/metadata-editor-ai.adapter.ts and spec when AI patch application is involved
src/lib/ai/metadata-editor-context-pack.ts and metadata-editor-ai-capabilities.ts when assistant grounding changes
- the owning dynamic-fields component/descriptor for the same control
Coverage Rules
- Every critical runtime metadata property should have visual coverage or an explicitly documented advanced JSON fallback.
- JSON-only support is not acceptable for common authoring paths such as labels, placeholders, validators, icons, clear buttons, option sources, entity lookup, presentation, submit policy, and accessibility.
EditorProperty.name dot paths must match canonical FieldMetadata paths or documented metadata-editor paths.
- Groups, hints, labels, placeholders, and options must use the metadata-editor i18n path when the lib has catalog coverage.
- Icon fields should use Material Symbols guidance such as
mi:...; ordinary prefix/suffix text must not receive icon-only hints.
controlType must be normalized through core helpers and must exist in both dynamic-fields discovery and metadata-editor config coverage.
- Metadata-editor may select and materialize a
controlType, but it must not mint package-owned
control identities. Unknown controls should fail through the dynamic-fields/core discovery path
instead of creating a local editor-only type.
- Inline filter coverage must stay complete for
INLINE_FILTER_CONTROL_TYPE_VALUES; aliases should
resolve through resolveInlineFilterEditorProperties(...), and unknown aliases should remain
unsupported rather than receiving a guessed editor config.
ConfigRegistryService and EditorProperty[] arrays are the visual coverage catalog for metadata
editing. They should expose canonical paths with typed editor controls; advanced JSON textareas are
acceptable only for genuinely structured/legacy escape hatches and should be documented as such.
- Renderer coverage proves that metadata can be authored and round-tripped visually; it does not prove
that the owning dynamic-field, option-source provider, backend endpoint, entity lookup runtime,
inline overlay, or AI authoring profile executes that behavior. When adding paths such as
optionSource.*, payloadMode, selection policy, detail/create actions, or inline control
properties, also point to the owning runtime/profile evidence before documenting the capability as
active.
- For remote select/list/entity authoring, prefer governed fields such as
resourcePath and
optionSource.* over legacy endpoint properties. configs-remote-source.spec.ts is the boundary
proof: common select-like configs should not reintroduce endpoint, while entity lookup visual
coverage must expose RESOURCE_ENTITY metadata including key/type/entity/resource paths, identity,
display, dependency, selection policy, capabilities, detail/create actions, dialog, and payload
mode paths. Do not hide these common paths behind a JSON-only textarea or host-local editor patch.
- AI-assisted metadata editing must use declared manifest operations such as
controlType.set,
renderer.configure, and inline/presentation operations. The adapter must reject free-form
seed/controlType patches and JSON-only coverage for required visual authoring.
renderer.configure is a registry/editor-coverage operation, not a consumer seed patch. In the
current adapter it requires a specialized runtime/editor handler and must not be compiled into a
local seed or FieldMetadata patch. If a migration needs new visual coverage, update the owning
EditorProperty[] catalog, renderer registry/factory evidence, specs, and AI manifest/context
evidence instead of teaching the consumer or assistant to mutate one screen's metadata directly.
Renderer And Form Factory
DynamicEditorRendererComponent renders EditorProperty[] into grouped form rows through DynamicFieldLoaderDirective. DynamicFormFactoryService creates controls by dot path and attaches contextual validators. Do not bypass that path with local component-specific forms unless the editor property type itself is missing and needs to be added to the registry.
When adding an editor property:
- Confirm the runtime component actually consumes the metadata.
- Add or update the correct
*.config.ts.
- Ensure
SchemaNormalizerService hydrates seed defaults correctly for complex values.
- Ensure
DynamicFormFactoryService creates the control at the correct dot path.
- Add/update focused coverage specs.
- If the property claims runtime behavior beyond visual round-trip, verify the owning
dynamic-fields/runtime/option-source skill evidence and keep unsupported paths marked as partial,
declared-only, or JSON-only.
- Update AI manifest/context-pack/capabilities if the visual coverage is AI-authorable.
- Update docs/checklists if coverage status changed.
Validation
Use focused gates:
- renderer layout or grouping:
components/dynamic-editor-renderer/dynamic-editor-renderer.component.spec.ts
- field host/control-type resolution:
components/field-metadata-editor/field-metadata-editor.component.spec.ts
- inline/dynamic-fields parity:
config/inline-editor-coverage.spec.ts
- remote option/entity lookup visual coverage:
config/configs-remote-source.spec.ts plus the owning
dynamic-fields option-source/runtime evidence when behavior, not only editor materialization, changed
- form factory dot-path/control creation:
testing/dynamic-form-factory.service.spec.ts
- schema normalization for defaults/complex values:
testing/schema-normalizer.service.spec.ts
- i18n catalog behavior:
i18n/metadata-editor.i18n.spec.ts
- AI manifest/adapter coverage:
ai/praxis-metadata-editor-authoring-manifest.spec.ts and ai/metadata-editor-ai.adapter.spec.ts
- compile surface:
ng build praxis-metadata-editor
Use praxis-angular-public-api-governance for root exports and praxis-angular-validation-gates to decide whether a consumer E2E is needed.
1---2name: praxis-metadata-editor-renderer-coverage3description: "Use when implementing, reviewing, or auditing `@praxisui/metadata-editor` renderer coverage: `FieldMetadataEditorComponent`, `DynamicEditorRendererComponent`, `EditorProperty[]` configs, inline editor coverage, dynamic-fields parity, form factory controls, visual coverage versus JSON-only fallback, hints, i18n labels, and public API for metadata editor components/services."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-metadata-editor-renderer-coverage6---78# Praxis Metadata Editor Renderer Coverage910Use this skill for visual metadata authoring coverage in `@praxisui/metadata-editor`. The editor owns the UI that edits canonical `FieldMetadata`; it does not render final form fields at runtime and it must not duplicate `@praxisui/dynamic-fields` component semantics.1112When locating files, first resolve the Angular workspace root. Paths below are relative to13`praxis-ui-angular/projects/praxis-metadata-editor` unless another package is explicitly named.1415## Canonical Boundary1617`@praxisui/metadata-editor` owns:1819- `FieldMetadataEditorComponent`20- `DynamicEditorRendererComponent`21- `ConfigRegistryService`22- `EditorComponentRegistryService`23- `EditorProperty[]` config catalogs under `src/lib/config/*.config.ts`24- `DynamicFormFactoryService`25- `SchemaNormalizerService`26- metadata-editor AI adapter, manifest, context pack, and capability catalog when visual coverage is AI-authorable27- visual coverage docs/checklists2829`@praxisui/dynamic-fields` owns the actual field components, control type discovery, descriptors, and runtime interpretation. When a dynamic-field runtime property is missing from the editor, add visual coverage in metadata-editor; do not copy runtime component logic into the editor.3031## Required Source Audit3233Inspect before editing:3435- `projects/praxis-metadata-editor/AGENTS.md`36- `README.md`37- `docs/metadata-editors-architecture.praxis.md`38- `docs/EDITOR-COVERAGE-CHECKLIST.md`39- `docs/HINTS-STYLE-GUIDE.md`40- `src/public-api.ts`41- `src/lib/components/field-metadata-editor/field-metadata-editor.component.ts`42- `src/lib/components/dynamic-editor-renderer/dynamic-editor-renderer.component.ts`43- `src/lib/config/*.config.ts` for the affected control type44- `src/lib/config/inline-filter-control-properties.map.ts` when inline filter coverage is involved45- `src/lib/config/inline-editor-coverage.spec.ts`46- `src/lib/services/schema-normalizer.service.ts`47- `src/lib/services/dynamic-form-factory.service.ts`48- `src/lib/registry/config-registry.service.ts`49- `src/lib/ai/praxis-metadata-editor-authoring-manifest.ts` and spec when the surface is AI-authorable50- `src/lib/ai/metadata-editor-ai.adapter.ts` and spec when AI patch application is involved51- `src/lib/ai/metadata-editor-context-pack.ts` and `metadata-editor-ai-capabilities.ts` when assistant grounding changes52- the owning dynamic-fields component/descriptor for the same control5354## Coverage Rules5556- Every critical runtime metadata property should have visual coverage or an explicitly documented advanced JSON fallback.57- JSON-only support is not acceptable for common authoring paths such as labels, placeholders, validators, icons, clear buttons, option sources, entity lookup, presentation, submit policy, and accessibility.58- `EditorProperty.name` dot paths must match canonical `FieldMetadata` paths or documented metadata-editor paths.59- Groups, hints, labels, placeholders, and options must use the metadata-editor i18n path when the lib has catalog coverage.60- Icon fields should use Material Symbols guidance such as `mi:...`; ordinary prefix/suffix text must not receive icon-only hints.61- `controlType` must be normalized through core helpers and must exist in both dynamic-fields discovery and metadata-editor config coverage.62- Metadata-editor may select and materialize a `controlType`, but it must not mint package-owned63 control identities. Unknown controls should fail through the dynamic-fields/core discovery path64 instead of creating a local editor-only type.65- Inline filter coverage must stay complete for `INLINE_FILTER_CONTROL_TYPE_VALUES`; aliases should66 resolve through `resolveInlineFilterEditorProperties(...)`, and unknown aliases should remain67 unsupported rather than receiving a guessed editor config.68- `ConfigRegistryService` and `EditorProperty[]` arrays are the visual coverage catalog for metadata69 editing. They should expose canonical paths with typed editor controls; advanced JSON textareas are70 acceptable only for genuinely structured/legacy escape hatches and should be documented as such.71- Renderer coverage proves that metadata can be authored and round-tripped visually; it does not prove72 that the owning dynamic-field, option-source provider, backend endpoint, entity lookup runtime,73 inline overlay, or AI authoring profile executes that behavior. When adding paths such as74 `optionSource.*`, `payloadMode`, selection policy, detail/create actions, or inline control75 properties, also point to the owning runtime/profile evidence before documenting the capability as76 active.77- For remote select/list/entity authoring, prefer governed fields such as `resourcePath` and78 `optionSource.*` over legacy `endpoint` properties. `configs-remote-source.spec.ts` is the boundary79 proof: common select-like configs should not reintroduce `endpoint`, while entity lookup visual80 coverage must expose `RESOURCE_ENTITY` metadata including key/type/entity/resource paths, identity,81 display, dependency, selection policy, capabilities, detail/create actions, dialog, and payload82 mode paths. Do not hide these common paths behind a JSON-only textarea or host-local editor patch.83- AI-assisted metadata editing must use declared manifest operations such as `controlType.set`,84 `renderer.configure`, and inline/presentation operations. The adapter must reject free-form85 `seed`/`controlType` patches and JSON-only coverage for required visual authoring.86- `renderer.configure` is a registry/editor-coverage operation, not a consumer seed patch. In the87 current adapter it requires a specialized runtime/editor handler and must not be compiled into a88 local `seed` or `FieldMetadata` patch. If a migration needs new visual coverage, update the owning89 `EditorProperty[]` catalog, renderer registry/factory evidence, specs, and AI manifest/context90 evidence instead of teaching the consumer or assistant to mutate one screen's metadata directly.9192## Renderer And Form Factory9394`DynamicEditorRendererComponent` renders `EditorProperty[]` into grouped form rows through `DynamicFieldLoaderDirective`. `DynamicFormFactoryService` creates controls by dot path and attaches contextual validators. Do not bypass that path with local component-specific forms unless the editor property type itself is missing and needs to be added to the registry.9596When adding an editor property:97981. Confirm the runtime component actually consumes the metadata.992. Add or update the correct `*.config.ts`.1003. Ensure `SchemaNormalizerService` hydrates seed defaults correctly for complex values.1014. Ensure `DynamicFormFactoryService` creates the control at the correct dot path.1025. Add/update focused coverage specs.1036. If the property claims runtime behavior beyond visual round-trip, verify the owning104 dynamic-fields/runtime/option-source skill evidence and keep unsupported paths marked as partial,105 declared-only, or JSON-only.1067. Update AI manifest/context-pack/capabilities if the visual coverage is AI-authorable.1078. Update docs/checklists if coverage status changed.108109## Validation110111Use focused gates:112113- renderer layout or grouping: `components/dynamic-editor-renderer/dynamic-editor-renderer.component.spec.ts`114- field host/control-type resolution: `components/field-metadata-editor/field-metadata-editor.component.spec.ts`115- inline/dynamic-fields parity: `config/inline-editor-coverage.spec.ts`116- remote option/entity lookup visual coverage: `config/configs-remote-source.spec.ts` plus the owning117 dynamic-fields option-source/runtime evidence when behavior, not only editor materialization, changed118- form factory dot-path/control creation: `testing/dynamic-form-factory.service.spec.ts`119- schema normalization for defaults/complex values: `testing/schema-normalizer.service.spec.ts`120- i18n catalog behavior: `i18n/metadata-editor.i18n.spec.ts`121- AI manifest/adapter coverage: `ai/praxis-metadata-editor-authoring-manifest.spec.ts` and `ai/metadata-editor-ai.adapter.spec.ts`122- compile surface: `ng build praxis-metadata-editor`123124Use `praxis-angular-public-api-governance` for root exports and `praxis-angular-validation-gates` to decide whether a consumer E2E is needed.