@7365admin1/layer-common 4.35.1-staging.385 → 4.36.0

package/utils/hid-reader-selection.ts

@@ -1,52 +0,0 @@
-/**
- * WHICH HID READER THE OPERATOR IS WORKING ON — the one rule behind it.
- *
- * Every HID screen used to hold its own `ref("")` and default it to
- * `readers[0]`, so picking HID 2 on HID Reader Users and clicking through to
- * HID Cards put you back on HID 1. They are separate PAGES, so the component
- * unmounted and the ref was rebuilt from scratch every time — there was no way
- * to make a choice stick. "I am working on HID 2" is a mode, not a per-screen
- * preference.
- *
- * Navigation between those pages is a route change rather than a page load
- * (`NavigationItem.vue` renders the menu's `route` through `:to`), so the
- * module-scoped ref in `useHidReaderSelection` survives it. This file holds the
- * part worth testing: deciding whether a remembered choice may still be used.
- */
-
-export type HidReaderChoice = { siteId: string; readerId: string };
-
-/** Anything with an id — the four screens all carry a different reader shape. */
-type ReaderLike = { _id?: unknown };
-
-export const EMPTY_HID_READER_CHOICE: HidReaderChoice = { siteId: "", readerId: "" };
-
-/**
- * The reader a screen should show, given what this site actually has.
- *
- * A remembered id is honoured ONLY when it belongs to this site and is still in
- * the list. That single condition covers every way it goes stale:
- *
- * - the operator switched site, so the id belongs to a site they have left
- * - the reader was deleted or deactivated since they chose it
- * - nothing has been chosen yet
- *
- * In all three the first reader is returned instead. The alternative — using
- * the id anyway — sends requests for a reader the site does not own, which come
- * back empty and read on screen as a reader with no users, no cards and no
- * logs, rather than as the mistake it is.
- */
-export function resolveHidReaderId(
-  siteId: string,
-  readers: readonly ReaderLike[] | null | undefined,
-  choice: HidReaderChoice = EMPTY_HID_READER_CHOICE,
-): string {
-  const ids = (Array.isArray(readers) ? readers : [])
-    .map((reader) => String(reader?._id ?? ""))
-    .filter(Boolean);
-
-  if (choice.siteId === String(siteId ?? "") && ids.includes(choice.readerId)) {
-    return choice.readerId;
-  }
-  return ids[0] ?? "";
-}

package/utils/occupancy-role.ts

@@ -1,109 +0,0 @@
-/**
- * OWNER / OCCUPANT / PERSON IN CHARGE - the three standings a business
- * tenancy has, and everything the product says about them.
- *
- * One list, because three screens read it: the form that asks the question
- * (`PeopleFormMgmt`), the list and preview that print the answer back, and
- * the row menu that reassigns it (`people-mgmt`). The values are the ones the
- * server stores and validates - `OccupancyRoles` in core's `person.model.ts`
- * - so a value added on one side has to be added on the other.
- */
-export const OCCUPANCY_ROLE_OPTIONS: TOccupancyRoleOption[] = [
-  {
-    value: "owner",
-    title: "Owner",
-    action: "Assign Owner",
-    prompt: "Assign Owner",
-    description:
-      "The legal titleholder or primary deed owner of the property.",
-  },
-  {
-    value: "occupant",
-    title: "Occupant",
-    action: "Assign Occupant",
-    prompt: "Assign Occupant",
-    description:
-      "The person currently living in, renting, or utilizing the physical unit.",
-  },
-  {
-    value: "person-in-charge",
-    title: "Person in Charge",
-    action: "Assign Person in Charge",
-    prompt: "Assign Person in Charge (PIC)",
-    description:
-      "The designated manager responsible for maintenance, emergencies, and daily operations.",
-  },
-];
-
-/**
- * The same three, in the order the ROW MENU draws them, which is not the
- * order the form's radio does. Derived rather than re-typed so the wording
- * cannot drift between the two.
- */
-export const OCCUPANCY_ROLE_ACTIONS: TOccupancyRoleOption[] = (
-  ["person-in-charge", "owner", "occupant"] as TOccupancyRole[]
-).map(
-  (value) =>
-    OCCUPANCY_ROLE_OPTIONS.find(
-      (option) => option.value === value,
-    ) as TOccupancyRoleOption,
-);
-
-/**
- * The label for a stored role, or "" for a person who was never asked - which
- * is everyone on a residential site and everyone saved before the question
- * existed. Callers decide what to print instead; nobody should print a raw
- * `person-in-charge` at a user.
- */
-export function occupancyRoleLabel(role?: string | null): string {
-  return (
-    OCCUPANCY_ROLE_OPTIONS.find((option) => option.value === role)?.title ?? ""
-  );
-}
-
-/**
- * Does this person hold OWNER at their unit?
- *
- * The role when there is one, `isOwner` when there is not - the same test the
- * server applies (`holdsUnitOwner` in core's `unit-owner.util.ts`). A person
- * recorded before the role existed carries only the flag, and the people list
- * already prints them as "Owner".
- */
-export function holdsUnitOwner(person?: {
-  occupancyRole?: string | null;
-  isOwner?: boolean;
-}): boolean {
-  if (!person) return false;
-
-  if (person.occupancyRole) return person.occupancyRole === "owner";
-
-  return person.isOwner === true;
-}
-
-/**
- * MUST THIS PERSON HAND THE UNIT OVER BEFORE THEY CAN BE DEACTIVATED?
- *
- * The owner of a unit does not leave while they still own it - the standing
- * moves to another tenant at the same block, level and unit first.
- *
- * Keyed to the ROLE and never to `isOwner`, exactly as the server keys it
- * (`mustHandOverBeforeDeactivating` in core): the flag is on every resident in
- * the estate, and no residential screen can change it, so a rule keyed to it
- * would trap records that can never satisfy it.
- */
-export function mustHandOverBeforeDeactivating(person?: {
-  occupancyRole?: string | null;
-}): boolean {
-  return person?.occupancyRole === "owner";
-}
-
-/**
- * Why a deactivation was held back. The SERVER carries the enforcing copy of
- * this rule and of these words (core `unit-owner.util.ts`); this one exists so
- * the console can say it before the round trip rather than after.
- */
-export function ownerHandoverRequiredMessage(name?: string): string {
-  const who = name?.trim() ? `"${name.trim()}"` : "This person";
-
-  return `${who} is the owner of this unit. Assign the owner role to another tenant at the same block, level and unit before deactivating them.`;
-}

package/utils/robot-fleet-core.ts

@@ -1,57 +0,0 @@
-/**
- * HERO Fleet Core building helpers (pure, tested in test/robot-fleet-core.test.mjs).
- *
- * The fleet building (`GET /api/robots/fleet-core/building`) comes in the same
- * shape as a saved building map - levels / doors / lifts in the HERO plan frame -
- * plus live `doorStates` and `liftStates` in the lift / door contract shape.
- * Not part of the mobile-synced rules (`robot-display.ts`), so web only for now.
- */
-
-export const FLEET_CORE_BRAND = "fleet-core";
-
-/** Is this building the read-only fleet building rather than a saved map? */
-export const isFleetBuilding = (map: Record<string, any> | null | undefined) => map?.source === FLEET_CORE_BRAND;
-
-/** Does the site have fleet robots (then their building is the one to draw)? */
-export const hasFleetRobots = (rows: Array<Record<string, any>>) => rows.some((r) => r?.brand === FLEET_CORE_BRAND);
-
-/** "L2" -> 2, "B1" -> -1, "G" -> 0 (the fleet names its floors). */
-export function fleetFloorNo(name: unknown): number | null {
-  if (typeof name !== "string") return null;
-  const m = /^(L|B)(\d{1,3})$/i.exec(name.trim());
-  if (m) return m[1]!.toUpperCase() === "B" ? -Number(m[2]) : Number(m[2]);
-  return /^G$/i.test(name.trim()) ? 0 : null;
-}
-
-/** Names of the doors that read OPEN (door contract mode 2). */
-export function openDoorNames(map: Record<string, any> | null | undefined): Set<string> {
-  return new Set((map?.doorStates ?? []).filter((d: any) => d?.currentMode === 2).map((d: any) => String(d.doorName)));
-}
-
-/**
- * The fleet's lifts as lift-queue items (the shape `liftCard` reads): the car's
- * floor from the live state, and the robot holding the lift (its session is
- * "<fleet>/<robot>", our robotSn) as the one riding, from its floor to the
- * lift's destination. The fleet runs no waiting queue we can read.
- */
-export function fleetLiftItems(map: Record<string, any> | null | undefined, rows: Array<Record<string, any>>) {
-  if (!isFleetBuilding(map)) return [];
-  const states = new Map<string, any>((map!.liftStates ?? []).map((s: any) => [String(s.liftName), s]));
-  return (map!.lifts ?? []).map((lift: any) => {
-    const st = states.get(String(lift.name));
-    const current = fleetFloorNo(st?.currentFloor);
-    const dest = fleetFloorNo(st?.destinationFloor);
-    const holder = st?.sessionId ? rows.find((r) => r?.robotSn === st.sessionId) : null;
-    return {
-      liftName: String(lift.name),
-      floors: lift.floors ?? [],
-      state: { currentFloor: current },
-      active: holder
-        ? { _id: `fleet-${lift.name}`, robotId: String(holder._id), robotName: holder.name, fromFloor: current ?? dest, toFloor: dest ?? current }
-        : null,
-      queue: [],
-      recent: [],
-      simulated: false,
-    };
-  });
-}

package/utils/sp-inviter-row.ts

@@ -1,97 +0,0 @@
-/**
- * The inviting organisation's view of one service-provider invitation, in
- * words. Pure, so it is tested without a browser.
- *
- * The company name comes from the server (`companyName`: the company that
- * accepted, or the new company's name a sign-up invitation carried). While an
- * invitation is unanswered the company is genuinely not known yet - the cell
- * says so instead of drawing "-".
- */
-
-export type TSentInvitation = {
-  status?: string;
-  viewStatus?: string;
-  statusLabel?: string;
-  companyName?: string;
-  metadata?: Record<string, any>;
-  invitedByName?: string;
-  invitedAt?: string | null;
-  createdAt?: string | null;
-  answeredAt?: string | null;
-  onSite?: boolean;
-};
-
-const ANSWERED: Record<string, string> = {
-  complete: "Accepted",
-  declined: "Declined",
-  cancelled: "Cancelled",
-  rejected: "Not approved",
-  expired: "Expired",
-};
-
-type TNatureOption = { title?: string; value?: string };
-
-/**
- * The service type in words: the org's free-text nature if it gave one,
- * else the label from the nature-of-business list, else the raw stored code
- * ("security_agency") as a last resort. `useLocal` can hand back a plain
- * array or a ref-like `{ value }` wrapper - read whichever shape was passed.
- *
- * `nature` is NOT always free text: both `_getServiceProviders` and the
- * `customer.sites`-derived `getServiceProvidersForSite` aggregations in
- * @7365admin1/core set it to `organization.nature`, the SAME raw code `type`
- * carries ("security_agency") - not a human-typed description. Treating it as
- * free text made the raw code win over the label lookup for every row, since
- * `nature` is truthy whenever it is set at all. Only trust it as an override
- * when it is NOT itself one of the known codes.
- */
-export function spTypeLabel(type: string, nature: string | undefined, source: unknown): string {
-  const list = (Array.isArray(source) ? source : (source as any)?.value) as
-    | TNatureOption[]
-    | undefined;
-  const codeMatch = (value?: string) => list?.find((x) => x.value === value);
-
-  if (nature && String(nature).trim() && !codeMatch(nature)) return String(nature);
-
-  const hit = codeMatch(type) ?? codeMatch(nature);
-  return hit?.title ?? type ?? nature ?? "-";
-}
-
-export function spDay(value?: string | null): string {
-  if (!value) return "";
-  const d = new Date(value);
-  return Number.isNaN(d.getTime())
-    ? ""
-    : d.toLocaleDateString("en-GB", { day: "numeric", month: "short", year: "numeric" });
-}
-
-/** The company cell: the name, or why there is none yet. */
-export function sentCompany(row: TSentInvitation): { text: string; known: boolean } {
-  const name = String(row.companyName || row.metadata?.name || "").trim();
-  if (name) return { text: name, known: true };
-  const status = row.viewStatus || row.status || "";
-  return {
-    text: ["pending", "awaiting-approval"].includes(status) ? "Not accepted yet" : "Not accepted",
-    known: false,
-  };
-}
-
-/** "Invited by Tommy on 24 Sep 2026". */
-export function sentInvitedLine(row: TSentInvitation): string {
-  const who = String(row.invitedByName ?? "").trim();
-  const when = spDay(row.invitedAt ?? row.createdAt);
-  return [who ? `by ${who}` : "", when ? `on ${when}` : ""].filter(Boolean).join(" ");
-}
-
-/** The line under the status: when it was answered, and what it means now. */
-export function sentStatusLine(row: TSentInvitation): string {
-  const status = row.viewStatus || row.status || "";
-  const when = spDay(row.answeredAt);
-  if (status === "complete" && row.onSite === false) {
-    return `Accepted${when ? ` on ${when}` : ""} · no longer on this site`;
-  }
-  if (ANSWERED[status]) return when ? `${ANSWERED[status]} on ${when}` : "";
-  if (status === "awaiting-approval") return "Seven365 checks it before it is sent";
-  if (status === "pending") return "Sent - waiting for their answer";
-  return "";
-}