@expofp/schema - npm Package Compare versions

Comparing version 3.22.0 to 3.23.0

dist/lib/config.js

@@ -166,13 +166,13 @@ import * as z from 'zod';
      * The initial camera, applied once at boot (an empty object means "don't
-     * move"). The runtime counterpart is `FloorPlan.setCamera` / the `setCamera`
-     * intent; the legacy `?centerxy=`/`?center=`/`?z=`/`?bearing=`/`?zoomtime=`
-     * URL params translate into this shape.
+     * move"). The URL form is `?camera[x]=…`; the runtime counterpart is
+     * `FloorPlan.setCamera` / the `setCamera` intent.
      */
     camera: CameraSchema,
     /**
-     * Visibility of the map chrome, applied once at boot (an empty object leaves
-     * the chrome untouched; a non-empty one resets every omitted element to
-     * visible — the legacy `?hide=` list semantics). The runtime counterpart is
-     * `FloorPlan.setVisibility` / the `setVisibility` intent; the legacy
-     * `?hide=a,b` deep link keeps its store-level translation.
+     * Visibility of the map chrome, applied once at boot. An empty object leaves
+     * the chrome untouched; a non-empty one REBUILDS the set — every element it
+     * omits resets to visible — so a URL that hides one element must list every
+     * other element it also wants hidden. The URL form is
+     * `?visibility[header]=false`; the runtime counterpart is
+     * `FloorPlan.setVisibility` / the `setVisibility` intent.
      */
@@ -204,4 +204,6 @@ visibility: VisibilitySchema,
      * on-device SetKiosk flow wins; `localStorage['kiosk']='0'` disables both).
-     * Canonical URL form `?kiosk[x]=…`; the legacy `kiosk_*` params stay the
-     * per-navigation translation and `?kiosk=1/0` keeps toggling kiosk mode.
+     * Canonical URL form `?kiosk[x]=…`, and `?kiosk=1/0` keeps toggling kiosk
+     * mode. The legacy `kiosk_x/y/z` params are a separate, narrower channel:
+     * they carry the anchor POSITION to a phone scanning a kiosk's route QR
+     * code, and put that phone in no kiosk mode of its own.
      */
@@ -211,6 +213,7 @@ kiosk: KioskSchema,
 /**
- * Deprecated `allowConsent` input alias, accepted by every input schema and
- * folded into `consent` by `loadConfig` (`true` → `'granted'`, `false` →
- * `'denied'`; a layer's own `consent` wins). The effective config never
- * carries it.
+ * Deprecated `allowConsent` input alias, accepted by the data and options input
+ * schemas and folded into `consent` by `loadConfig` (`true` → `'granted'`,
+ * `false` → `'denied'`; a layer's own `consent` wins). The effective config
+ * never carries it. RETIRED from the URL query — `?consent=` is the only query
+ * form (see `retiredKeys` in `@expofp/config`'s legacy-url codec).
  */
@@ -305,4 +308,5 @@ const DeprecatedConsentAlias = {
     // the former one-shot presentation params — the query keys keep their
-    // historical names, which match these field names exactly
-    noOverlay: true,
+    // historical names, which match these field names exactly. `noOverlay` is
+    // NOT among them: the overlay is addressed by `?visibility[overlay]=false`
+    // from the URL, the field stays a manifest/options setting
     monochrome: true,
@@ -331,3 +335,2 @@ hideHeaderLogo: true,
 })
-    .extend(DeprecatedConsentAlias)
     .extend(LoadDiagnostics);
@@ -334,0 +337,0 @@ /**

dist/lib/kiosk.d.ts

@@ -7,6 +7,12 @@ import * as z from 'zod';
  * and wins over the config; the `localStorage['kiosk']='0'` device switch
- * disables both). The legacy `kiosk_*` URL params stay the per-navigation
- * translation of this same shape (QR-shared routes smuggle the anchor through
- * them), and `?kiosk=1/0` keeps toggling kiosk MODE — the mode and the anchor
- * are independent inputs.
+ * disables both). `?kiosk=1/0` keeps toggling kiosk MODE — the mode and the
+ * anchor are independent inputs.
+ *
+ * The legacy `kiosk_x/y/z` params are a narrower, per-navigation channel for
+ * one purpose: a kiosk's route QR code hands the scanning phone the anchor
+ * POSITION so the route's missing starting point resolves there. The framing
+ * fields below travel only in this node, never through those params. Note that
+ * the scanning phone does end up in kiosk mode and stays there — a pre-existing
+ * quirk of how the anchor is stored, not an intended property of the channel;
+ * `packages/floorplan/src/components/Kiosk/kioskUrlParam.ts` traces it.
  */
@@ -13,0 +19,0 @@ export declare const KioskSchema: z.ZodObject<{

dist/lib/kiosk.js

@@ -7,6 +7,12 @@ import * as z from 'zod';
  * and wins over the config; the `localStorage['kiosk']='0'` device switch
- * disables both). The legacy `kiosk_*` URL params stay the per-navigation
- * translation of this same shape (QR-shared routes smuggle the anchor through
- * them), and `?kiosk=1/0` keeps toggling kiosk MODE — the mode and the anchor
- * are independent inputs.
+ * disables both). `?kiosk=1/0` keeps toggling kiosk MODE — the mode and the
+ * anchor are independent inputs.
+ *
+ * The legacy `kiosk_x/y/z` params are a narrower, per-navigation channel for
+ * one purpose: a kiosk's route QR code hands the scanning phone the anchor
+ * POSITION so the route's missing starting point resolves there. The framing
+ * fields below travel only in this node, never through those params. Note that
+ * the scanning phone does end up in kiosk mode and stays there — a pre-existing
+ * quirk of how the anchor is stored, not an intended property of the channel;
+ * `packages/floorplan/src/components/Kiosk/kioskUrlParam.ts` traces it.
  */
@@ -13,0 +19,0 @@ export const KioskSchema = z.object({

package.json

 {
   "name": "@expofp/schema",
-  "version": "3.22.0",
+  "version": "3.23.0",
   "type": "module",
@@ -28,3 +28,3 @@ "description": "ExpoFP SDK internal: expo data schemas and types",
   "devDependencies": {
-    "@expofp/utils": "3.22.0"
+    "@expofp/utils": "3.23.0"
   },
@@ -31,0 +31,0 @@ "files": [

No alert changes

Improved metrics

Total package byte prevSize

181586

0.6%

Lines of code

4206

0.31%

No dependency changes