cedar-embeddable-editor 2.0.18 → 2.0.19

package/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.19] - 2026-10-02
+
+Aligns with `cedar-model-typescript-library@1.0.15`.
+
+- Includes `reveal` for taking the user to a field, data quality problems located by the entries that hold them, and stored problems shown at their fields.
+
 ## [2.0.18] - 2026-09-26
 
 Aligns with `cedar-model-typescript-library@1.0.15`.
@@ -21,6 +27,17 @@ Aligns with `cedar-model-typescript-library@1.0.13`.
 
 ### Added
 
+- `reveal(location, options)` on `cedar-embeddable-editor`, which takes the user to a field or
+  element: it turns to the field's page, moves each repeating field or element above it to the
+  named entry, opens the panels around it, scrolls it into view and focuses its control.
+  `{ focus: false }` scrolls without taking focus. It resolves to whether the field could be
+  shown, and changes nothing when it cannot. A problem from the data quality report is itself a
+  location, so a host listing the problems can pass each one straight to `reveal`.
+- `occurrences` on each data quality problem: the entry of each repeating field or element along
+  its path, outermost first. A path alone names one place per entry of everything above it, so a
+  host could not say which entry held a bad value. The same bad value in two entries is now two
+  problems.
+
 - A second element, `cedar-embeddable-field`, registered by the same bundle. It renders one field's
   control and nothing of the form around it, for a host that holds a field artifact rather
   than a template — a designer collecting a default value, above all. The value goes in and
@@ -44,6 +61,18 @@ Aligns with `cedar-model-typescript-library@1.0.13`.
 
 ### Changed
 
+- A field shows what is wrong with a value loaded from a stored instance as soon as the form opens.
+  The error states waited for the control to be edited or touched, so a field the data quality
+  report listed as invalid showed nothing. An empty required field still waits, until the user
+  edits it or is taken to it with `reveal`.
+- The data quality report states at the field the problems no control can find: a stored choice
+  that is not one of the options, a term missing its label or its IRI, an authority identifier
+  that is not a valid IRI, and a list longer than its `maxItems`. A list shorter than its
+  `minItems` is stated once the user is taken to it.
+- The data quality report no longer reports `missingProperty`. It described a repeating field or
+  element absent from the instance CEE read, which CEE writes out as an empty list, so it warned
+  about a defect that saving removed and that no field could show.
+
 - A numeric field's type constraint and a temporal field's errors follow the configured
   language. The numeric sentence was English written into the validator, and the temporal
   widget printed the data quality report's diagnostics, such as `Granularity is year, but the
@@ -85,6 +114,9 @@ Aligns with `cedar-model-typescript-library@1.0.13`.
 
 ### Fixed
 
+- `minItems` and `maxItems` on a repeating field inside a repeating element are checked in
+  every entry of the element. They were checked in the entry on screen, so the report changed
+  with the page the user had moved to.
 - Reassigning `cedar-embeddable-field.fieldObject` recreates the control even when the field type
   stays the same, so validators and other initialized settings follow the new artifact.
 - `cedar-embeddable-field` emits `valueChange` when validity changes even if the normalized value

package/README.md

@@ -124,13 +124,40 @@ takes the same page apart step by step, and
 [Embedding in a Framework](https://metadatacenter.readthedocs.io/en/latest/cedar-embeddable-editor/frameworks/)
 covers Angular, React, and Ember.
 
+A dialog host can set `previewMode: true` in either read-only or editable mode
+to omit CEE's identity header and use compact, content-sized form spacing. Template
+descriptions and page navigation remain available. `readOnlyMode` independently
+controls whether values can be edited. Ordinary embeds retain their existing layout.
+
+Trial hosts such as Workspace “Try out” and CED’s editable preview set
+`suppressEmptyFieldErrors: true`. Clearing a control then hides its error state and
+messages even after blur. Nonempty invalid values and incomplete temporal values still
+show errors. This affects presentation only: required fields remain invalid in the quality
+report. Ordinary metadata editing leaves the option off.
+
 ## Embedding a Single Field
 
-The bundle registers a second element. `<cedar-embeddable-field>` renders one field's
-control — the same control the editor renders for that field, from the same component
-— and nothing of the form around it: no label, no description, no card. A host that
-holds a field artifact rather than a template puts this where the control belongs and
-draws the rest itself.
+The bundle registers a second element. `<cedar-embeddable-field>` renders one field
+from its artifact. In editable mode it supplies the same bare control CEE uses,
+so a host such as CED can place it in its own form.
+
+With `config = { readOnlyMode: true }`, CEF owns the full presentation: label,
+field type, description, constraints, choices, sources and declared defaults where
+present. The type is named by the icon beside the label. A supplied value is shown
+read-only. CEE uses the same field presentation, so preview hosts only need to supply
+the artifact and their dialog shell.
+
+Set `previewMode: true` with `readOnlyMode: true` when the host supplies the field name
+in its own header. CEF then omits its header, and with it the type icon, while
+retaining the description and value or specification. A host whose header leaves out
+the type, such as the Workspace's preview, also sets `showFieldType: true`.
+CEF then states the type above the description, with the icon its header would have
+drawn (for example, `Paragraph`). A host whose header already shows the type, as CED's
+field cards do, leaves it unset.
+
+Read-only controls have no placeholder text, and fields without constraints draw empty
+boxes. Static fields show their content. A standalone page break is described without
+creating pagination.
 
 Designing a template is what this is for. An author giving a field a default value
 needs somewhere to type it, and the box that collects one has to be the control the

package/bundle-manifest.host-fonts.json

@@ -4,6 +4,6 @@
     "main.js",
     "polyfills.js"
   ],
-  "bytes": 2182095,
-  "sha256": "b37efb9f7c3e893b74d2a4a7eaf784fcbd7b0b54586f25a93f6c8d7c596ad73c"
+  "bytes": 2207976,
+  "sha256": "3420439a5f96c136ee9fe2552891041c826e76496f5663416633c56d1e14082b"
 }

package/bundle-manifest.json

@@ -4,6 +4,6 @@
     "main.js",
     "polyfills.js"
   ],
-  "bytes": 2365905,
-  "sha256": "8e62f446b41da71eaf8c46be9818a78e66639d3b2de7e170de7a06edb991b121"
+  "bytes": 2391786,
+  "sha256": "daa2df903e9bfb833dd69fa7827d79b22f7148eacf283979452cbfaa9a842535"
 }

package/cedar-embeddable-editor.d.ts

@@ -45,6 +45,16 @@ export type CeeConfigKey = keyof CeeConfig;
  */
 export interface CeeConfig {
     showTemplateDescription?: boolean;
+    /** Embedding with a host-provided heading, in either read-only or editable mode. Hides CEE's identity header or CEF's field header; keeps descriptions and controls. */
+    previewMode?: boolean;
+    /**
+     * For a read-only CEF preview whose host heading does not name the field's type. The hidden header
+     * carried the icon that names it, so CEF states the type above the description instead, with that
+     * icon. A host whose own heading already shows the type leaves this unset.
+     */
+    showFieldType?: boolean;
+    /** Keep empty trial fields quiet without changing validity or nonempty-value errors. */
+    suppressEmptyFieldErrors?: boolean;
     /**
      * Renders the form without editing controls.
      *
@@ -151,6 +161,16 @@ export interface CeeValidationProblem {
     code: string;
     /** Path to the offending value, outermost first. */
     path: string[];
+    /**
+     * The entry taken at each repeating field or element along `path`, outermost first.
+     *
+     * A path names one place per entry of everything above it that repeats, and this
+     * says which entry holds the problem. A problem about a whole list, such as
+     * `minItems`, names the entries above the list and none of its own; a `required`
+     * problem names none, because any entry would satisfy it. Pass the problem to
+     * `reveal` to take the user to it.
+     */
+    occurrences: number[];
     /** The field's property name, which is the last path segment. */
     field: string;
     /** The field's declared `_ui.inputType`, or null where it declares none. */
@@ -160,6 +180,31 @@ export interface CeeValidationProblem {
     /** The value that failed, when there is one. */
     value?: unknown;
 }
+/**
+ * A place on the form: a field or element, in particular entries of what repeats.
+ *
+ * A `CeeValidationProblem` is one, so a host can pass a problem straight to `reveal`.
+ */
+export interface CeeLocation {
+    /** Component path from the template root, as a problem's `path` gives it. */
+    path: string[];
+    /**
+     * The entry to show at each repeating field or element along `path`, outermost first.
+     *
+     * Optional, and may be shorter than the repeating components along the path: those
+     * it does not reach stay on the entry they show.
+     */
+    occurrences?: number[];
+}
+/** What a host may ask of `reveal` beyond showing the field. */
+export interface CeeRevealOptions {
+    /**
+     * Whether to move keyboard focus to the field's control. Defaults to true. A host
+     * keeping focus in its own controls, such as a designer showing the field it has
+     * selected, passes false.
+     */
+    focus?: boolean;
+}
 /**
  * What CEE thinks of the instance currently in the form.
  *
@@ -319,6 +364,20 @@ export interface CedarEmbeddableEditorElement extends HTMLElement {
     readonly currentMetadataYaml: string;
     /** What CEE thinks of the instance. Read-only. */
     readonly dataQualityReport: CeeDataQualityReport;
+    /**
+     * Take the user to a field or element, and resolve whether it could be shown.
+     *
+     * Turns to the field's page, moves each repeating field or element above it to the
+     * named entry, opens the panels around it, scrolls it into view and focuses its
+     * control. A field the user is taken to also states an unanswered requirement, which
+     * a field nobody has reached keeps quiet.
+     *
+     * Resolves false, having changed nothing, for a path the template does not declare,
+     * a hidden field, or an entry that does not exist. A repeating element with no
+     * entries stops the reveal at the element, since nothing inside it is on the form.
+     * Available once the element is in the document and has a template.
+     */
+    readonly reveal: (location: CeeLocation, options?: CeeRevealOptions) => Promise<boolean>;
 }
 /**
  * What one field holds, in the terms its own type is written in.
@@ -380,23 +439,20 @@ export interface CedarEmbeddableFieldChangeDetail {
  *
  * The subset of `CeeConfig` that describes a field rather than the form around one.
  * The keys left out — the download menu, the expand controls, the template
- * description — settle what an editor draws around its fields, and this element draws
- * nothing around its own.
+ * description — settle what an editor draws around a whole form. Field labels and
+ * descriptions belong to this element in read-only mode.
  */
-export type CedarEmbeddableFieldConfig = Pick<CeeConfig, 'readOnlyMode' | 'trustTemplateRichText' | 'terminologyBaseUrl' | 'bridgeBaseUrl' | 'defaultLanguage' | 'fallbackLanguage' | 'languageMapPathPrefix'>;
+export type CedarEmbeddableFieldConfig = Pick<CeeConfig, 'readOnlyMode' | 'previewMode' | 'showFieldType' | 'suppressEmptyFieldErrors' | 'trustTemplateRichText' | 'terminologyBaseUrl' | 'bridgeBaseUrl' | 'defaultLanguage' | 'fallbackLanguage' | 'languageMapPathPrefix'>;
 /**
  * One field's control, as a host sees it.
  *
- * Registered as `cedar-embeddable-field`. It renders exactly the widget the editor
- * renders for that field — the same component, not a second implementation — and
- * reports what the widget holds. Around it there is nothing: no label, no description,
- * no card. A host that has a field artifact and wants a value for it draws its own
- * surroundings and puts this where the control goes.
+ * Registered as `cedar-embeddable-field`. Editable, it renders the same bare value
+ * control as CEE, for a host that supplies its own surrounding form.
  *
- * Read-only is the presentation half of the same element. Editable, the field is a
- * control to fill in; read-only with nothing in it, the widget is replaced by a
- * statement of what the field will accept, which is what the editor shows when it
- * renders a template nobody has filled in yet.
+ * Read-only, it owns the complete field presentation shared with CEE: label, type,
+ * description and applicable constraints, choices, sources and defaults. A supplied
+ * value remains visible and cannot be edited. Static content is also described;
+ * a standalone page break has a label and type but does not create pagination.
  *
  * A field artifact carries no requiredness and no cardinality — both belong to a
  * field's deployment in a template, and this element deploys nothing — so the value