@camstack/ui-library 1.2.220 → 1.2.222

package/dist/composites/device-list/columns.d.ts

@@ -76,7 +76,7 @@ export declare const COLUMN_BREAKPOINT_CLASS: Record<DeviceColumnId, string>;
  * left to scroll under the pin — the pinned column simply holds its width
  * permanently and pushes Preview off the right edge. On a phone the viewport
  * is narrower than the pinned column alone, which is the reported defect:
- * "il nome alla sinistra è fixed, dovrebbe scorrere naturalmente."
+ * "il nome alla sinistra è fixed, dovrebbe scorrere naturalmente." [the name on the left is fixed, it should scroll naturally.]
  *
  * So the pin starts at `md`, the same width at which `features` returns and a
  * column exists to scroll under it. Below `md` the name column scrolls with

package/dist/index.cjs

@@ -19762,7 +19762,7 @@ function zoomLabel(spanMs) {
 *
 * *"Possiamo utilizzare lo stesso componente della sezione recording con la
 * timebar dove selezionare un periodo e mostrare le clip solo di quella banda
-* selezionata, espandibile."* — the operator, 2026-09-20. So this is not a
+* selezionata, espandibile."* [We can use the same component as the recording section with the timebar where a period can be selected and show the clips of that selected band only, expandable.] — the operator, 2026-09-20. So this is not a
 * second timebar: it is `TimelineControls` and `EventHeatmap`, the two pieces
 * `RecordingTimeline` is itself built from, over the same
 * `recording-timeline-model` (`dayWindow`, `panWindow`,
@@ -20611,7 +20611,7 @@ function resolveClipsView(input) {
 * Io in realtà utilizzerei la stessa tab recordings, lì abbiamo già tutto il
 * necessario, una nuova sezione alla fine per le clips dove possiamo
 * selezionare le source con un multiselect common, non componenti nuovi
-* anonimi."* So every piece of chrome here is a component this repo already
+* anonimi."* [The UI is horrible, it does not follow our UI at all … I would actually use the same recordings tab, we already have everything necessary there, a new section at the end for the clips where we can select the sources with a common multiselect, no new anonymous components.] So every piece of chrome here is a component this repo already
 * has: `Select`, `DataTable`, `EmptyState`, `ErrorBox`, `Pagination`, `Card`,
 * `Badge`, `Button`, `Skeleton`. What the chrome CARRIES is unchanged, and it
 * is the feature:
@@ -20633,7 +20633,7 @@ function resolveClipsView(input) {
 * It shipped with its own `‹ day ›` pair and the operator replaced it the same
 * way he replaced the chrome: *"Possiamo utilizzare lo stesso componente della
 * sezione recording con la timebar dove selezionare un periodo e mostrare le
-* clip solo di quella banda selezionata, espandibile."* So the list follows a
+* clip solo di quella banda selezionata, espandibile."* [We can use the same component as the recording section with the timebar where a period can be selected and show the clips of that selected band only, expandable.] So the list follows a
 * BAND (D564) — `TimelineControls` for the day, the zoom and the pan,
 * `EventHeatmap` for picking a narrower window out of it, both of them the
 * pieces `RecordingTimeline` is itself built from, over the same
@@ -20656,7 +20656,7 @@ function resolveClipsView(input) {
 * configuration that lives somewhere else. The operator put it exactly:
 * *"non è affatto necessario lo stato di abilitato o meno delle sources. Loro
 * vivono lì, ad esempio hksv c'è se la camera è esportata su homekit, reolink
-* la dà di suo così come il camstack."* HKSV is there if the camera is
+* la dà di suo così come il camstack."* [the enabled-or-not state of the sources is not necessary at all. They live there, for example hksv is there if the camera is exported to homekit, reolink provides it on its own, as does camstack.] HKSV is there if the camera is
 * exported to HomeKit; the Reolink source is there because Reolink is that
 * camera's provider; CamStack's is always there. None of that is a decision to
 * make in a clips list, so this surface offers no switch and writes no
@@ -20667,7 +20667,7 @@ function resolveClipsView(input) {
 *
 * The operator asked for *"un multiselect common"* while `listClips` still
 * took `sources?: string[]`. It now takes ONE `provider` —
-* *"l'utilizzatore è uno solo"* — and a multi-pick control over a
+* *"l'utilizzatore è uno solo"* [there is only one user] — and a multi-pick control over a
 * one-at-a-time argument offers a sum the hub cannot answer. So the control is
 * the shared single-choice one, `Select`: the same component the Recordings
 * page's own camera picker uses, which is what *"segue la nostra UI"* means
@@ -32895,7 +32895,7 @@ function resolveTableLayout({ mode, columnCount, isNarrow }) {
 *     where labels can be inferred. The operator can still see every
 *     stat / action — no horizontal scroll, no clipped text. The user
 *     directive: "molta informazione in poco spazio quando la width è
-*     bassa."
+*     bassa." [a lot of information in little space when the width is low.]
 *
 *   • **L2 — Standard** (`sm` — `640–1023px`, tablet + small laptop)
 *     2-column grids, side panels become visible, button labels return.
@@ -39438,12 +39438,17 @@ function PopoverRowAction({ icon: Icon, title, children }) {
 }
 //#endregion
 //#region src/lib/resolve-sensor-display.ts
+/** Table keys are canonical spellings; providers often send `C` / `F` / `celsius`. */
+function canonUnit(raw) {
+	if (raw === void 0) return void 0;
+	return (0, _camstack_types.normalizeUnit)(raw) ?? raw;
+}
 var identity = (raw) => raw;
 function resolveSensorDisplay(input) {
 	const perCap = input.capName !== void 0 ? input.display?.perCap?.[input.capName] : void 0;
 	const precision = perCap?.precision ?? input.display?.precision ?? input.roleDefault?.precision ?? input.slicePrecision;
-	const sourceUnit = input.sliceUnit ?? input.canonicalUnit;
-	const overrideUnit = perCap?.unit ?? input.display?.unit ?? input.roleDefault?.unit;
+	const sourceUnit = canonUnit(input.sliceUnit ?? input.canonicalUnit);
+	const overrideUnit = canonUnit(perCap?.unit ?? input.display?.unit ?? input.roleDefault?.unit);
 	if (overrideUnit !== void 0 && sourceUnit !== void 0 && overrideUnit !== sourceUnit && (0, _camstack_types.canConvertUnit)(sourceUnit, overrideUnit)) return {
 		unit: overrideUnit,
 		precision,

package/dist/index.js

@@ -13,7 +13,7 @@ import * as __mfHostReactDOMClient from "react-dom/client";
 import { createRoot } from "react-dom/client";
 import * as __mfHostTrpcClient from "@trpc/client";
 import { createTRPCClient, createWSClient, httpLink, splitLink, wsLink } from "@trpc/client";
-import { ALL_CAPABILITY_DEFINITIONS, CAM_PROFILE_ORDER, CLIP_STILL_DISPOSITION_HEADER, CLIP_STILL_REASON_CODE_HEADER, CLIP_STILL_REASON_HEADER, CONTAINER_CHILD_PRIORITY, DEFAULT_EVENTS_BAND_BUFFER_SEC, DEFAULT_EVENT_COLOR, DEVICE_TYPE_CONTROL_KIND, DISPLAY_ICON_GROUPS, DeviceExportStatusSchema, DeviceFeature, DeviceRole, DeviceType, EVENT_TAXONOMY, EXTENSION_SLOTS, EXTENSION_SLOT_IDS, EventCategory, ExposedDeviceSchema, FIRST_LEVEL_MACRO_CLASSES, KNOWN_CAP_NAMES, MAX_SENSOR_TRIGGER_DEVICES, MODEL_PROVIDER_IDS, NAVIGATION_LIGHT_LEVEL_MAX, NAVIGATION_LIGHT_LEVEL_MIN, PET_FEEDER_MANUAL_FEED_MAX, PET_FEEDER_MANUAL_FEED_MIN, RECORDING_AUDIO_TRIGGER_OFFERED_DBFS, RECORDING_SOURCE_CAMSTACK_ADDON, RecordingConfigSchema, RecordingStatusSchema, SOURCE_CAP_ACTIVE_FIELD, STATIONARY_OVERLAY_STYLE, TIMEZONES, buildModelVariantGroups, canConvertUnit, clusterStepSettingFieldsFor, createDeviceProxy, createLazyTrpcSource, createSliceHandle, deriveRecordingMode, describeModelVariant, findTimezone, formatParkedFor, publicEventCategories, resolveContainerPrimaryChild, resolveDeviceControlKind, resolveRecordingProfiles, resolveVariantModelId, resolveViewableDeviceIds, searchDisplayIcons, selectAssignedProfileSlots, tryConvertUnit } from "@camstack/types";
+import { ALL_CAPABILITY_DEFINITIONS, CAM_PROFILE_ORDER, CLIP_STILL_DISPOSITION_HEADER, CLIP_STILL_REASON_CODE_HEADER, CLIP_STILL_REASON_HEADER, CONTAINER_CHILD_PRIORITY, DEFAULT_EVENTS_BAND_BUFFER_SEC, DEFAULT_EVENT_COLOR, DEVICE_TYPE_CONTROL_KIND, DISPLAY_ICON_GROUPS, DeviceExportStatusSchema, DeviceFeature, DeviceRole, DeviceType, EVENT_TAXONOMY, EXTENSION_SLOTS, EXTENSION_SLOT_IDS, EventCategory, ExposedDeviceSchema, FIRST_LEVEL_MACRO_CLASSES, KNOWN_CAP_NAMES, MAX_SENSOR_TRIGGER_DEVICES, MODEL_PROVIDER_IDS, NAVIGATION_LIGHT_LEVEL_MAX, NAVIGATION_LIGHT_LEVEL_MIN, PET_FEEDER_MANUAL_FEED_MAX, PET_FEEDER_MANUAL_FEED_MIN, RECORDING_AUDIO_TRIGGER_OFFERED_DBFS, RECORDING_SOURCE_CAMSTACK_ADDON, RecordingConfigSchema, RecordingStatusSchema, SOURCE_CAP_ACTIVE_FIELD, STATIONARY_OVERLAY_STYLE, TIMEZONES, buildModelVariantGroups, canConvertUnit, clusterStepSettingFieldsFor, createDeviceProxy, createLazyTrpcSource, createSliceHandle, deriveRecordingMode, describeModelVariant, findTimezone, formatParkedFor, normalizeUnit, publicEventCategories, resolveContainerPrimaryChild, resolveDeviceControlKind, resolveRecordingProfiles, resolveVariantModelId, resolveViewableDeviceIds, searchDisplayIcons, selectAssignedProfileSlots, tryConvertUnit } from "@camstack/types";
 import { createSystem } from "@camstack/sdk";
 import { z } from "zod";
 //#region ../../node_modules/lucide-react/dist/esm/shared/src/utils/mergeClasses.js
@@ -19738,7 +19738,7 @@ function zoomLabel(spanMs) {
 *
 * *"Possiamo utilizzare lo stesso componente della sezione recording con la
 * timebar dove selezionare un periodo e mostrare le clip solo di quella banda
-* selezionata, espandibile."* — the operator, 2026-09-20. So this is not a
+* selezionata, espandibile."* [We can use the same component as the recording section with the timebar where a period can be selected and show the clips of that selected band only, expandable.] — the operator, 2026-09-20. So this is not a
 * second timebar: it is `TimelineControls` and `EventHeatmap`, the two pieces
 * `RecordingTimeline` is itself built from, over the same
 * `recording-timeline-model` (`dayWindow`, `panWindow`,
@@ -20587,7 +20587,7 @@ function resolveClipsView(input) {
 * Io in realtà utilizzerei la stessa tab recordings, lì abbiamo già tutto il
 * necessario, una nuova sezione alla fine per le clips dove possiamo
 * selezionare le source con un multiselect common, non componenti nuovi
-* anonimi."* So every piece of chrome here is a component this repo already
+* anonimi."* [The UI is horrible, it does not follow our UI at all … I would actually use the same recordings tab, we already have everything necessary there, a new section at the end for the clips where we can select the sources with a common multiselect, no new anonymous components.] So every piece of chrome here is a component this repo already
 * has: `Select`, `DataTable`, `EmptyState`, `ErrorBox`, `Pagination`, `Card`,
 * `Badge`, `Button`, `Skeleton`. What the chrome CARRIES is unchanged, and it
 * is the feature:
@@ -20609,7 +20609,7 @@ function resolveClipsView(input) {
 * It shipped with its own `‹ day ›` pair and the operator replaced it the same
 * way he replaced the chrome: *"Possiamo utilizzare lo stesso componente della
 * sezione recording con la timebar dove selezionare un periodo e mostrare le
-* clip solo di quella banda selezionata, espandibile."* So the list follows a
+* clip solo di quella banda selezionata, espandibile."* [We can use the same component as the recording section with the timebar where a period can be selected and show the clips of that selected band only, expandable.] So the list follows a
 * BAND (D564) — `TimelineControls` for the day, the zoom and the pan,
 * `EventHeatmap` for picking a narrower window out of it, both of them the
 * pieces `RecordingTimeline` is itself built from, over the same
@@ -20632,7 +20632,7 @@ function resolveClipsView(input) {
 * configuration that lives somewhere else. The operator put it exactly:
 * *"non è affatto necessario lo stato di abilitato o meno delle sources. Loro
 * vivono lì, ad esempio hksv c'è se la camera è esportata su homekit, reolink
-* la dà di suo così come il camstack."* HKSV is there if the camera is
+* la dà di suo così come il camstack."* [the enabled-or-not state of the sources is not necessary at all. They live there, for example hksv is there if the camera is exported to homekit, reolink provides it on its own, as does camstack.] HKSV is there if the camera is
 * exported to HomeKit; the Reolink source is there because Reolink is that
 * camera's provider; CamStack's is always there. None of that is a decision to
 * make in a clips list, so this surface offers no switch and writes no
@@ -20643,7 +20643,7 @@ function resolveClipsView(input) {
 *
 * The operator asked for *"un multiselect common"* while `listClips` still
 * took `sources?: string[]`. It now takes ONE `provider` —
-* *"l'utilizzatore è uno solo"* — and a multi-pick control over a
+* *"l'utilizzatore è uno solo"* [there is only one user] — and a multi-pick control over a
 * one-at-a-time argument offers a sum the hub cannot answer. So the control is
 * the shared single-choice one, `Select`: the same component the Recordings
 * page's own camera picker uses, which is what *"segue la nostra UI"* means
@@ -32871,7 +32871,7 @@ function resolveTableLayout({ mode, columnCount, isNarrow }) {
 *     where labels can be inferred. The operator can still see every
 *     stat / action — no horizontal scroll, no clipped text. The user
 *     directive: "molta informazione in poco spazio quando la width è
-*     bassa."
+*     bassa." [a lot of information in little space when the width is low.]
 *
 *   • **L2 — Standard** (`sm` — `640–1023px`, tablet + small laptop)
 *     2-column grids, side panels become visible, button labels return.
@@ -39414,12 +39414,17 @@ function PopoverRowAction({ icon: Icon, title, children }) {
 }
 //#endregion
 //#region src/lib/resolve-sensor-display.ts
+/** Table keys are canonical spellings; providers often send `C` / `F` / `celsius`. */
+function canonUnit(raw) {
+	if (raw === void 0) return void 0;
+	return normalizeUnit(raw) ?? raw;
+}
 var identity = (raw) => raw;
 function resolveSensorDisplay(input) {
 	const perCap = input.capName !== void 0 ? input.display?.perCap?.[input.capName] : void 0;
 	const precision = perCap?.precision ?? input.display?.precision ?? input.roleDefault?.precision ?? input.slicePrecision;
-	const sourceUnit = input.sliceUnit ?? input.canonicalUnit;
-	const overrideUnit = perCap?.unit ?? input.display?.unit ?? input.roleDefault?.unit;
+	const sourceUnit = canonUnit(input.sliceUnit ?? input.canonicalUnit);
+	const overrideUnit = canonUnit(perCap?.unit ?? input.display?.unit ?? input.roleDefault?.unit);
 	if (overrideUnit !== void 0 && sourceUnit !== void 0 && overrideUnit !== sourceUnit && canConvertUnit(sourceUnit, overrideUnit)) return {
 		unit: overrideUnit,
 		precision,

package/dist/lib/responsive.d.ts

@@ -14,7 +14,7 @@
  *     where labels can be inferred. The operator can still see every
  *     stat / action — no horizontal scroll, no clipped text. The user
  *     directive: "molta informazione in poco spazio quando la width è
- *     bassa."
+ *     bassa." [a lot of information in little space when the width is low.]
  *
  *   • **L2 — Standard** (`sm` — `640–1023px`, tablet + small laptop)
  *     2-column grids, side panels become visible, button labels return.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/ui-library",
-  "version": "1.2.220",
+  "version": "1.2.222",
   "type": "module",
   "main": "dist/index.cjs",
   "module": "dist/index.js",