@7365admin1/layer-common 4.1.3-staging.257 → 4.2.0

package/CHANGELOG.md

@@ -1,5 +1,58 @@
 # @iservice365/layer-common
 
+## 4.2.0
+
+### Minor Changes
+
+- 8fa8aff: Add a bulk camera import, and make the camera settings list reach past ten.
+
+  `CameraBulkImportDialog` takes the technician camera survey sheet as a CSV,
+  previews every row with the server's own verdict before anything is saved, and
+  then commits. Preview and commit are the same server call, so the preview
+  cannot disagree with what is written. `is_anpr` rows are refused by name, and
+  the screen states which surveyed columns a camera record cannot store.
+
+  `CameraMain` now loads the site's whole camera list in server pages of 100
+  (five pages maximum), searches it by name or address, and pages it locally. It
+  previously fetched page 1 with no `limit` against a server default of 10, so
+  cameras 11 and up were unreachable from the settings panel.
+
+  `useSiteSettings` gains `limit` on `getAllSiteCameras` and a new
+  `bulkImportSiteCameras`.
+
+- 050712c: Camera setup can start from the recorder instead of a finished address.
+
+  A CCTV camera's stored address is a relay player page — nothing printed on a camera and nothing in a
+  recorder's own screens will tell somebody what it is, so until now it had to be requested from
+  whoever runs the video service and pasted in. The form now offers two ways to say where a camera is:
+  "From the recorder" (recorder address, optional port, channel number — the three things a person can
+  actually read off a recorder, which the server turns into the address it stores) and "I already have
+  a link", which is the existing URL field unchanged.
+
+  Editing an existing camera still opens on the URL field, so nothing about a record that already
+  works changes shape. A "Test this camera" button checks the address before saving, server-side: the
+  browser never contacts a recorder and never sees a credential.
+
+### Patch Changes
+
+- c919902: HID face registration: the photo is no longer shown or held once registration completes.
+  The user enrollment, reader roster and access-log screens report enrollment state instead of
+  a face thumbnail, none of them fetch the reader's image any more, and the captured image is
+  discarded when the save finishes, on success and on failure alike. Enrollment state
+  (`facialEnrolled`, `facialEnrolledAt`, `facialData`, `imageTimestamp`) is saved explicitly so
+  editing a user cannot un-enroll them. Re-enrolling now takes a fresh capture.
+- 2cdbecb: Say what 0 means in the subscription plan's Max seats field
+- f3d2e68: Search and page the camera picker on the monitoring wall.
+
+  The picker column rendered one checkbox per camera with no filter, no pager and no count. At a
+  150-camera site the last camera was reachable only by scrolling past the other 149 in a 220 px
+  column, and nothing on screen said how many there were — so a supervisor who could not find a camera
+  had no way to tell whether it was missing or merely further down.
+
+  It now shows 25 at a time with a search box and a "26-50 of 150" range. The paging rule lives in
+  `utils/camera-wall.ts` as `pickerView` so it is covered by tests rather than only by the template,
+  which the playground build does not compile.
+
 ## 4.1.2
 
 ### Patch Changes
@@ -330,11 +383,11 @@
   `utils/console-tier.ts` + `composables/useConsoleTier.ts` mirror the server's
   own rule from two endpoints the console already calls, unprojected:
 
-              GET /api/members/user/:user/app/admin    the Seven365 staff membership
-              GET /api/roles/id/:role                  that membership's role document
+                GET /api/members/user/:user/app/admin    the Seven365 staff membership
+                GET /api/roles/id/:role                  that membership's role document
 
-              owner  = member.type === "admin" && role.type === "admin" && role.default === true
-              staff  = member.type === "admin" && role.type === "admin"
+                owner  = member.type === "admin" && role.type === "admin" && role.default === true
+                staff  = member.type === "admin" && role.type === "admin"
 
   `role.default` is the marker because it is the only property of a platform
   staff role no API caller can set - `role.controller.ts` validates create and

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.1.3-staging.257",
+  "version": "4.2.0",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",