@pnlight/sdk-react 0.1.0 → 0.2.0

package/README.md

@@ -62,10 +62,42 @@ the variable name through `count_variable`:
 The component subscribes to that DivKit variable and applies the same prepend
 animation for each increment.
 
+### Progress bar and animated number
+
+`schemaVersion: 3` documents can also use `pnlight.progress_bar` and
+`pnlight.animated_number`, with the same props as the iOS components. The bar
+animates from its current fill to a new `progress`, and the label counts
+through every value between the displayed number and a new `value`, so markup
+does not have to drive either with DivKit animations.
+
+The same reactivity rule applies: keep `progress` / `value` as the literal
+initial value and name the variable in `progress_variable` / `value_variable`.
+
+```json
+{
+  "type": "custom",
+  "custom_type": "pnlight.progress_bar",
+  "width": { "type": "match_parent" },
+  "height": { "type": "fixed", "value": 10 },
+  "custom_props": {
+    "instance_id": "scan",
+    "progress": 0,
+    "progress_variable": "scan_progress"
+  }
+}
+```
+
+Numbers are formatted with `Intl.NumberFormat` for the browser's locale, the
+web bar uses a CSS transition, and both components respect
+`prefers-reduced-motion`. On the web `track_height` is also the bar's minimum
+thickness, so give it the same value as any DivKit `height` thinner than its
+`8` default. In a `schemaVersion` 1 or 2 document neither
+`custom_type` is registered, matching the native version gate.
+
 ## PNLight actions
 
 Navigation, dialogs, and haptics are consumed inside the component for
-`schemaVersion: 2` documents. Observe them when needed:
+`schemaVersion: 2` and `schemaVersion: 3` documents. Observe them when needed:
 
 ```tsx
 <RemoteUi
@@ -94,6 +126,12 @@ explicit height when the document uses `match_parent`:
 - Missing `schemaVersion`, or version `1`, keeps legacy edge-to-edge behavior.
 - `schemaVersion: 2` enables PNLight flows, safe areas, scaling variables,
   dialogs, and haptics.
+- `schemaVersion: 3` preserves all v2 behavior, accepts SDK-owned typed
+  actions such as `pnlight.purchase`, and registers the `pnlight.progress_bar`
+  and `pnlight.animated_number` components. Web opens a simple purchase
+  simulator showing the product ID. `Success` executes `on_success`; `Fail`
+  closes the simulator without executing it. No real StoreKit transaction
+  occurs.
 - CTA, icon button, circular loader, animated prepend list, and Lottie support
   are additive.
 

package/dist/custom-components.d.ts

@@ -1,4 +1,17 @@
-export declare function registerPNLightComponents(): Map<string, {
+/**
+ * Discards state retained for a direct document mounted into a persistent host.
+ * Flow-route stores are keyed by their disposable route elements and become
+ * unreachable when the flow is destroyed.
+ */
+export declare function clearPNLightComponentSnapshots(host: Element): void;
+/**
+ * Registers the PNLight custom elements and maps them to their `custom_type`.
+ *
+ * Components introduced in a later schema version stay unmapped in an older
+ * document, matching the native renderer's version gate.
+ */
+export declare function registerPNLightComponents(schemaVersion?: RemoteUiSchemaVersion): Map<string, {
     element: string;
 }>;
+import { type RemoteUiSchemaVersion } from "./schema-version.js";
 //# sourceMappingURL=custom-components.d.ts.map

package/dist/custom-components.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom-components.d.ts","sourceRoot":"","sources":["../src/custom-components.ts"],"names":[],"mappings":"AAqgCA,wBAAgB,yBAAyB,IAAI,GAAG,CAAC,MAAM,EAAE;IAAE,OAAO,EAAE,MAAM,CAAA;CAAE,CAAC,CAqB5E"}
+{"version":3,"file":"custom-components.d.ts","sourceRoot":"","sources":["../src/custom-components.ts"],"names":[],"mappings":"AA2JA;;;;GAIG;AACH,wBAAgB,8BAA8B,CAAC,IAAI,EAAE,OAAO,GAAG,IAAI,CAIlE;AAm5CD;;;;;GAKG;AACH,wBAAgB,yBAAyB,CACvC,aAAa,GAAE,qBAA8C,GAC5D,GAAG,CAAC,MAAM,EAAE;IAAE,OAAO,EAAE,MAAM,CAAA;CAAE,CAAC,CAqBlC;AAMD,OAAO,EAGL,KAAK,qBAAqB,EAC3B,MAAM,qBAAqB,CAAC"}