cedar-embeddable-editor 2.0.19 → 2.0.20

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.20] - 2026-10-05
+
+Aligns with `cedar-model-typescript-library@1.0.16`.
+
+- Includes paragraph character limits, every stored constraint problem stated at its field in each language, checked host value shapes, read-only guards and immediate lookup cancellation.
+
 ## [2.0.19] - 2026-10-02
 
 Aligns with `cedar-model-typescript-library@1.0.15`.
@@ -112,6 +118,15 @@ Aligns with `cedar-model-typescript-library@1.0.13`.
 - Compact YAML downloads retain the template's root ID but omit the IDs of nested fields and
   elements. Full YAML downloads continue to carry the complete identity tree.
 
+- The form's header sets CEE's name and version stamp beside the mark rather than beneath it, so
+  the identity is no taller than the mark. Beside a title with a description, the identity and the
+  template's version and status keep to the top of the row, level with the title. At 520px or
+  narrower they take a row of their own above the title, which then has the full width.
+
+- Every text box carries `autocomplete="off"`. A browser otherwise listed beneath a field what had
+  been typed into any box with the same name or id, and Angular Material gives each input an id
+  such as `mat-input-3`, so the list could hold values from an unrelated form.
+
 ### Fixed
 
 - `minItems` and `maxItems` on a repeating field inside a repeating element are checked in

package/README.md

@@ -39,9 +39,9 @@ gives the input properties, the output properties, and the change event a host
 reads.
 
 For the design rationale, the architecture, and deployments in research
-platforms, see [*Author Once, Publish Everywhere: Portable Metadata Authoring
-with the CEDAR Embeddable Editor*](https://doi.org/10.5334/dsj-2026-002),
-published in the *Data Science Journal* (2026).
+platforms, see [_Author Once, Publish Everywhere: Portable Metadata Authoring
+with the CEDAR Embeddable Editor_](https://doi.org/10.5334/dsj-2026-002),
+published in the _Data Science Journal_ (2026).
 
 ## Installing
 
@@ -135,6 +135,23 @@ messages even after blur. Nonempty invalid values and incomplete temporal values
 show errors. This affects presentation only: required fields remain invalid in the quality
 report. Ordinary metadata editing leaves the option off.
 
+## Validation
+
+Read `dataQualityReport` for the whole instance, including nested and off-screen
+occurrences. Each problem has a code, `severity` (`warning` or `error`), a field
+`path` and occurrence indices. Pass a field problem to `reveal(problem)` to reach it.
+
+Missing required answers, insufficient occurrences and unnamed attribute rows are
+warnings. Invalid values, malformed incoming data and unfinished edits are errors.
+Either makes `isValid` false; the host decides whether saving is allowed. A required
+field must be answered in every existing containing element. A repeating field
+needs at least one answer within each such element.
+
+The report includes unfinished date/time and attribute-name edits, and `change`
+fires when metadata **or the report** changes. Invalid imported field IRIs and
+well-shaped numeric, temporal and IRI defaults remain available for correction.
+Terminology membership and server-side validation remain the host's responsibility.
+
 ## Embedding a Single Field
 
 The bundle registers a second element. `<cedar-embeddable-field>` renders one field
@@ -219,6 +236,20 @@ field?.addEventListener('valueChange', (event: CustomEvent<CedarEmbeddableFieldC
 the control afresh — the field being designed changes type under its author's hand.
 `config` takes one assignment, as the editor's does. A value of a kind the field
 cannot hold is reported through `eventHandler` and ignored rather than coerced.
+Malformed runtime payloads are also rejected, including assignments made before the
+field arrives. Accepted values and artifacts are copied; host mutation after an
+assignment does not change the editor. Getters and events return detached values.
+
+A numeric value has the shape `{ kind: 'number', value: number | string }`.
+Ordinary numbers remain numbers. When converting to a JavaScript number would lose
+significant digits or exceed its range, CEF returns the exact numeric string instead:
+`9007199254740993` and `0.1234567890123456789` retain every digit. Both forms may be
+assigned back through `value`. Constraint validity remains a separate result.
+
+Read-only mode guards user mutations in the controller, including late callbacks
+and structural edits. Explicit host `value` assignments still work. Controlled-term
+and external-authority searches cancel on a new query, a read-only transition, or
+widget destruction; an old response cannot overwrite a newer query.
 
 Requiredness and cardinality belong to a field's deployment inside a template, and
 this element deploys nothing, so the value it acquires is single and is allowed to be
@@ -412,3 +443,12 @@ for all available settings.
 
 3. In your browser, navigate to `http://localhost:4400/`. The app will
    automatically reload if you change any of the source files.
+
+The host lifecycle matrix in
+`src/app/modules/shared/components/wrapper-lifecycle-matrix.spec.ts` crosses three input
+arrival orders, host mutation, one or two simultaneous numeric/lookup wrapper pairs,
+ordinary/large-integer/precise-decimal values, initial/late/no read-only state,
+and superseded lookup success/error/completion (324 cases). It runs in `npm test`
+with real wrappers, artifact coordination, controllers and lookup streams; rendering
+and HTTP are substituted. The Angular coordinator suite separately verifies rendered
+controls, simultaneous wrappers, host events and malformed assignments.

package/bundle-manifest.host-fonts.json

@@ -4,6 +4,6 @@
     "main.js",
     "polyfills.js"
   ],
-  "bytes": 2207976,
-  "sha256": "3420439a5f96c136ee9fe2552891041c826e76496f5663416633c56d1e14082b"
+  "bytes": 2228152,
+  "sha256": "7fdb1fbd1a59b2cdc77e6c6d54716398809d6f3438ebe2c99272fde0e5a38647"
 }

package/bundle-manifest.json

@@ -4,6 +4,6 @@
     "main.js",
     "polyfills.js"
   ],
-  "bytes": 2391786,
-  "sha256": "daa2df903e9bfb833dd69fa7827d79b22f7148eacf283979452cbfaa9a842535"
+  "bytes": 2350430,
+  "sha256": "9cc4c9cb9e669d79bba195fdaaa3df9ea11228d54896783bc00ccd21e542d619"
 }

package/cedar-embeddable-editor.d.ts

@@ -157,6 +157,8 @@ export interface CeeTemplateAndInstance {
  * TypeScript host could not read either without a cast.
  */
 export interface CeeValidationProblem {
+    /** Missing answers are warnings; invalid values and unfinished edits are errors. Both affect isValid. */
+    severity: 'warning' | 'error';
     /** Machine-readable code, e.g. `numberType` or `temporalGranularity`. */
     code: string;
     /** Path to the offending value, outermost first. */
@@ -167,7 +169,7 @@ export interface CeeValidationProblem {
      * 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
+     * problem names the containing elements whose requirement is unfilled. Pass the problem to
      * `reveal` to take the user to it.
      */
     occurrences: number[];
@@ -224,15 +226,15 @@ export interface CeeDataQualityReport {
     /**
      * How many of those the instance fills.
      *
-     * A requirement is met when any occurrence carries a value, so this is
-     * unaffected by which page the form is showing.
+     * A required field needs at least one value in every existing containing element.
+     * This is unaffected by which occurrence the form is showing.
      */
     nonNullRequiredFieldValueCount: number;
     /**
      * Validation problems.
      *
-     * Includes one `required` problem for each unsatisfied required field
-     * declaration, while the two counters retain their existing aggregate view.
+     * Includes a located `required` warning for each containing element with an
+     * unanswered requirement. The two counters count declarations, not occurrences.
      */
     problems: CeeValidationProblem[];
     /** True when every required field is filled and no constraint is violated. */
@@ -358,7 +360,16 @@ export interface CedarEmbeddableEditorElement extends HTMLElement {
      * Replacing one is traced, so a page whose messages stop arriving can see why.
      */
     eventHandler: CeeEventHandler;
-    /** The instance as CEDAR JSON. Read-only. */
+    /**
+     * The instance as CEDAR JSON. Read-only.
+     *
+     * An empty object while the editor holds no artifact. An input it refuses because it is not a
+     * readable CEDAR artifact leaves it holding none, so a host that assigns a template on its own, or a
+     * template and instance together through `templateAndInstanceObject`, reads an empty object straight
+     * after the assignment as a refusal. An instance assigned on its own is held while it waits for a
+     * template, so a template refused after it leaves this holding the instance. The refusal's reason
+     * goes to the event handler's `error`.
+     */
     readonly currentMetadata: CeeJsonObject;
     /** The instance as CEDAR YAML. Read-only. */
     readonly currentMetadataYaml: string;
@@ -390,7 +401,7 @@ export interface CedarEmbeddableEditorElement extends HTMLElement {
  * Embeddable Designer's single `defaultValue: string` has.
  *
  * `none` is an unfilled field. It is also what a numeric field reports while it holds
- * something that is not yet a number, `3.` on the way to `3.5`; `valid` on the change
+ * something that is not yet a number, `-` on the way to `-3.5`; `valid` on the change
  * detail separates that from empty.
  */
 export type CedarEmbeddableFieldValue = {
@@ -401,10 +412,10 @@ export type CedarEmbeddableFieldValue = {
     kind: 'literal';
     value: string;
 }
-/** A numeric field, once what it holds is a finite number. */
+/** A numeric field. Exact decimal strings preserve values a JavaScript number would round. */
  | {
     kind: 'number';
-    value: number;
+    value: number | string;
 }
 /** A date or time, as the ISO literal its granularity calls for. */
  | {
@@ -454,10 +465,11 @@ export type CedarEmbeddableFieldConfig = Pick<CeeConfig, 'readOnlyMode' | 'previ
  * 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
- * it acquires is single and is allowed to be absent. That is what makes it usable for
- * a default value, which is optional by definition.
+ * Cardinality belongs to a field's deployment in a template, and this element deploys
+ * nothing, so the value it acquires is single. Requiredness is the field's own: an
+ * artifact that states `requiredValue: true` has an empty value reported as missing,
+ * unless the host sets `suppressEmptyFieldErrors`. CED writes a field on its own with
+ * `requiredValue: false`, which is what leaves a default value free to be empty.
  */
 export interface CedarEmbeddableFieldElement extends HTMLElement {
     /** Typed value event; the inherited overloads still handle every other DOM event. */