@camstack/addon-agent-ui 1.2.119 → 1.2.120

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/addon.js +11 -7
  2. package/package.json +1 -1
package/dist/addon.js CHANGED
@@ -5361,7 +5361,7 @@ var ZodIssueCode = {
5361
5361
  var ZodFirstPartyTypeKind;
5362
5362
  ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
5363
5363
  //#endregion
5364
- //#region ../types/dist/sleep-Bs3xPtSh.mjs
5364
+ //#region ../types/dist/sleep-GU_us3DG.mjs
5365
5365
  /**
5366
5366
  * The audio chunk plane's byte format, and the ONE expansion from a coded
5367
5367
  * window to float samples (D455).
@@ -27199,11 +27199,15 @@ DeviceType.Light, DeviceType.Siren, DeviceType.Switch, method(object({
27199
27199
  *
27200
27200
  * Adding a fifth name to that list would have been the wrong fix twice over:
27201
27201
  * that page is per-camera DETECTION tuning, and a grid's geometry belongs
27202
- * beside PTZ and motion zones on the camera itself which is exactly where the
27203
- * framework already puts a widget, when the widget is declared on a CAPABILITY.
27204
- * `deviceConfig.ui` is the mechanism (`motion-zones`, `ptz`, `ptz-autotrack`
27205
- * all use it): the framework emits the structural section and the widget
27206
- * self-persists through the cap's own mutations.
27202
+ * beside PTZ and motion zones on the camera itself. The device page is
27203
+ * BINDING-driven (D12), so the way in is a capability bound to the device —
27204
+ * and this cap carries its section the way `recording` does, by RETURNING it
27205
+ * from `getDeviceSettingsContribution`.
27206
+ *
27207
+ * Seven other widgets are still declared the other way, through a
27208
+ * `deviceConfig.ui` block the framework derives a section from. That route
27209
+ * gives the addon no say in where its own panel lands and no way to decline
27210
+ * for a device the panel does not suit, which is why this one does not use it.
27207
27211
  *
27208
27212
  * ## Why one addon may implement it
27209
27213
  *
@@ -40456,7 +40460,7 @@ var AgentUIAddon = class extends BaseAddon {
40456
40460
  capability: adminUiCapability,
40457
40461
  provider: {
40458
40462
  getStaticDir: async () => ({ staticDir: path.resolve(__dirname) }),
40459
- getVersion: async () => ({ version: "1.2.119" })
40463
+ getVersion: async () => ({ version: "1.2.120" })
40460
40464
  }
40461
40465
  }];
40462
40466
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-agent-ui",
3
- "version": "1.2.119",
3
+ "version": "1.2.120",
4
4
  "description": "Agent UI — lightweight status dashboard served by every agent node",
5
5
  "keywords": [
6
6
  "camstack",