bank20baht-ui 0.7.4 → 0.8.1

package/README.md

@@ -5,6 +5,7 @@ Components (Lit, light DOM) with a pure-TypeScript rules core.
 
 ```
 npm i bank20baht-ui
+npm i flatpickr   # peer dependency — only if you render date fields / <baht-datepicker>
 ```
 
 ## Quick start — one form (Level 1)
@@ -313,13 +314,22 @@ await registerElements(['baht-button', 'baht-avatar']);
 ```
 
 ```css
-/* 3. split stylesheets instead of the all-in-one tokens.css (139 KB) */
+/* 3. split stylesheets instead of the all-in-one tokens.css (~115 KB) */
 @import 'bank20baht-ui/css/tokens.css'; /* custom properties only, 18 KB */
 @import 'bank20baht-ui/css/components.css'; /* .baht-* classes */
-@import 'bank20baht-ui/css/datepicker.css'; /* flatpickr base + re-skin — only with <baht-datepicker> / date fields */
 ```
 
-`bank20baht-ui/tokens.css` stays the one-import sheet (all three, flatpickr included).
+`bank20baht-ui/tokens.css` = the two sheets above in one import. The calendar is opt-in:
+
+```css
+/* with <baht-datepicker> / date fields — flatpickr's base sheet + the token re-skin */
+@import 'bank20baht-ui/css/datepicker.css';
+```
+
+flatpickr itself is a **peer dependency** (`npm i flatpickr`) loaded with a dynamic
+`import()` the first time a `<baht-datepicker>` mounts, so apps without date fields never
+bundle it and apps with them get it as its own chunk. `await el.updateComplete` on the
+element resolves once the calendar is attached.
 
 ## One install, typed everywhere
 

package/dist/components/baht-form.d.ts

@@ -26,7 +26,7 @@ export declare class BahtForm extends BahtElement {
      * but getData() still returns the FULL form — the server always validates
      * the complete schema, views never change the submit payload.
      */
-    view?: string;
+    view?: string | undefined;
     /**
      * Feature-flag values (spec 01 §12) — fields whose `flag` is off behave as
      * if they were never in the schema: no render, no validation, no payload.
@@ -58,6 +58,11 @@ export declare class BahtForm extends BahtElement {
     private warnedViews;
     /** applyFlags result, memoized on (form, flags) identity. */
     private flagCache;
+    /**
+     * `form` as the host may actually have left it: a framework can connect the element
+     * before it binds the property, so internally it is optional until then.
+     */
+    private get assignedForm();
     private get effectiveForm();
     protected willUpdate(changed: Map<PropertyKey, unknown>): void;
     /**
@@ -73,6 +78,15 @@ export declare class BahtForm extends BahtElement {
      */
     private clearDependents;
     private get sortedFields();
+    /**
+     * Visibility as of the last completed render, by key. A field that was
+     * hidden there and is visible now gets `baht-field--revealed` for one
+     * render so the stylesheet can fade it in; fields visible from the first
+     * render never animate (a form should not shimmer on mount).
+     */
+    private lastVisible;
+    private nextVisible;
+    private revealClass;
     private stateFor;
     private valueFor;
     /** Debounced keystrokes still in a control land in `edits` before anyone reads them. */
@@ -116,6 +130,8 @@ export declare class BahtForm extends BahtElement {
      * `renderField`/`.baht-error`). No-op for 'change'/'submit' modes. */
     private onFieldBlur;
     private renderField;
+    private uploaderFor;
+    private renderFieldMsg;
     /**
      * Resolve the descriptor at event time — it may have changed since the control
      * was first rendered (the same node is reused across renders, see render()).