cedar-embeddable-editor 2.0.29 → 2.0.30

package/CHANGELOG.md

@@ -5,6 +5,14 @@ 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.30] - 2026-10-27
+
+Aligns with `cedar-model-typescript-library@1.0.25`.
+
+- Adds a `required` setting to the field element's configuration. The aligned model library no longer lets a field written on its own state a requirement, so a host that places the field as required now says so in this setting.
+- Keeps a host page's Material theme from restyling the editor, by binding every Material token CEE reads on its own shadow host.
+- Registers the embedded fonts once in the document head rather than in every shadow root, and compiles the shadow-root stylesheet once rather than into both elements. The production bundle no longer carries the developer app, lodash or the whole `package.json`, and its manifest records the version the bundle reports as `reportedVersion`.
+
 ## [2.0.29] - 2026-10-26
 
 Aligns with `cedar-model-typescript-library@1.0.24`.

package/README.md

@@ -220,6 +220,14 @@ CEF then states the type above the description, with the icon its header would h
 drawn (for example, `Paragraph`). A host whose header already shows the type, as CED's
 field cards do, leaves it unset.
 
+A field written on its own is not required, because only a template or an element
+requires the field it places. A host that places the field as required sets
+`required: true`. CEF then marks the field as CEE marks a required one, and reports an
+empty value as missing unless `suppressEmptyFieldErrors` is set. Like every key, it
+takes one assignment, so a change of requirement takes a new element. CEF refuses an
+artifact that states a requirement or a recommendation itself, as both CEDAR model
+libraries do.
+
 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.

package/bundle-manifest.host-fonts.json

@@ -4,6 +4,7 @@
     "main.js",
     "polyfills.js"
   ],
-  "bytes": 2355685,
-  "sha256": "7fc9a98446692f4ed154ba514ccf5d76a91fbd0ac2d1620300df216ea1dbde84"
+  "bytes": 2236112,
+  "sha256": "3595bcec8380948ece0f2b9d529f265e3be55363f629f9caf556fe63dfdb949e",
+  "reportedVersion": "2.0.30"
 }

package/bundle-manifest.json

@@ -4,6 +4,7 @@
     "main.js",
     "polyfills.js"
   ],
-  "bytes": 2477991,
-  "sha256": "ff95b623a32bb05593f6297063a4ea3f0957bdd1450db3a4f091b5ff90cff0f8"
+  "bytes": 2358766,
+  "sha256": "87ec2da47f8efa70bd7d8b7fa8d05a8126ac807a21f878fd098607b0284ce3d6",
+  "reportedVersion": "2.0.30"
 }

package/cedar-embeddable-editor.d.ts

@@ -55,6 +55,15 @@ export interface CeeConfig {
     showFieldType?: boolean;
     /** Keep empty trial fields quiet without changing validity or nonempty-value errors. */
     suppressEmptyFieldErrors?: boolean;
+    /**
+     * For CEF: whether the field is required where the host places it.
+     *
+     * A field written on its own is not required, because only a template or an element requires the
+     * field it places. A host placing the field in a form of its own says so here. CEF then marks the
+     * field as CEE marks a required one, and reports an empty value as missing unless
+     * `suppressEmptyFieldErrors` is set. CEE reads its fields' requirements from the template.
+     */
+    required?: boolean;
     /**
      * Renders the form without editing controls.
      *
@@ -540,7 +549,7 @@ export interface CedarEmbeddableFieldChangeDetail {
  * 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' | 'previewMode' | 'showFieldType' | 'suppressEmptyFieldErrors' | 'trustTemplateRichText' | 'terminologyBaseUrl' | 'bridgeBaseUrl' | 'defaultLanguage' | 'fallbackLanguage' | 'languageMapPathPrefix'>;
+export type CedarEmbeddableFieldConfig = Pick<CeeConfig, 'readOnlyMode' | 'previewMode' | 'showFieldType' | 'suppressEmptyFieldErrors' | 'required' | 'trustTemplateRichText' | 'terminologyBaseUrl' | 'bridgeBaseUrl' | 'defaultLanguage' | 'fallbackLanguage' | 'languageMapPathPrefix'>;
 /**
  * One field's control, as a host sees it.
  *
@@ -552,11 +561,12 @@ 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.
  *
- * 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.
+ * Cardinality and requirement belong to a field's placement in a template, and a field
+ * written on its own states neither, so the value this element acquires is single. A
+ * host that places the field as required says so with the `required` configuration
+ * key. Like the rest of the configuration it takes one assignment, so a change of
+ * requirement takes a new element. An artifact that states a requirement or a
+ * recommendation itself is refused, as both CEDAR model libraries refuse one.
  */
 export interface CedarEmbeddableFieldElement extends HTMLElement {
     /** Typed value event; the inherited overloads still handle every other DOM event. */