Add a value summary extension so a feature's typed value can be displayed compactly in collection views (e.g., table columns). Use when a feature or property editor already has a value type and needs a renderer for collection table cells. Two variants — simple (element only, no API call) and resolver (batch API resolution needed). Prerequisite: a value type constant must already exist — use the general-add-value-type skill first if it doesn't.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Add a value summary extension so a feature's typed value can be displayed compactly in collection views (e.g., table columns). Use when a feature or property editor already has a value type and needs a renderer for collection table cells. Two variants — simple (element only, no API call) and resolver (batch API resolution needed). Prerequisite: a value type constant must already exist — use the general-add-value-type skill first if it doesn't.
Add Value Summary
Add a valueSummary extension so a feature's values are rendered in collection views.
Foundational documentation
Read before proceeding:
Value Summary — extension type, base classes, resolver contract, rules
Prerequisite
A value type constant (UMB_{FEATURE}_VALUE_TYPE) must already exist and be exported from the package index.ts. If it doesn't exist yet, use the general-add-value-type skill first.
What you need from the user
Feature name — kebab-case (e.g., color-picker, user-group)
Package path — where the feature lives (e.g., src/packages/property-editors/color-picker/)
Value type constant — the existing constant to bind to (e.g., UMB_COLOR_PICKER_VALUE_TYPE)
Resolver needed? — Yes if rendering requires an API call (resolving IDs to names). No if the raw value can be formatted directly.
If resolver is needed, also ask:
5. Resolved type — the TypeScript type after resolution (e.g., UmbUserGroupItemModel)
6. Repository to use — which item/detail repository resolves the values
Option A: Simple summary (no resolver)
Use when the raw value can be formatted or rendered without an API call — dates, booleans, strings, color hex codes, numeric ranges, etc.
import { manifests as valueSummaryManifests } from'./value-summary/manifests.js';
exportconstmanifests: Array<UmbExtensionManifest> = [
...valueSummaryManifests,
// ... other manifests
];
Simple summary checklist
Element extends UmbValueSummaryElementBase and exports as element
Manifest uses kind: 'default', correct forValueType, lazy element import
Manifests wired into parent manifests.ts
Compiles: npm run compile
Option B: Summary with resolver (batch API resolution)
Use when displaying the value requires fetching data — e.g., resolving reference uniques to display names. The resolver receives all values from the entire column in one batch call.
Same pattern as Option A, Step 1. Pass {TResolved} as the generic instead of {TValue} — the element receives the resolved value in this._value, already correctly typed.
