@7365admin1/module-hygiene 4.29.0 → 4.29.1-staging.13

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@7365admin1/module-hygiene",
   "license": "MIT",
-  "version": "4.29.0",
+  "version": "4.29.1-staging.13",
   "author": "7365admin1",
   "main": "dist/index.js",
   "module": "dist/index.mjs",
@@ -13,7 +13,7 @@
     "build": "tsup src/index.ts --format cjs,esm --dts",
     "release": "yarn run build && changeset publish",
     "lint": "tsc",
-    "test": "tsup src/utils/hygiene-dashboard-metrics.util.ts src/utils/hygiene-checkout-decision.util.ts --format esm --out-dir test/.build --no-dts --silent && node --test \"test/*.test.mjs\""
+    "test": "tsup src/utils/hygiene-dashboard-metrics.util.ts src/utils/hygiene-checkout-decision.util.ts src/utils/completion-photo.util.ts --format esm --out-dir test/.build --no-dts --silent && node --test \"test/*.test.mjs\""
   },
   "devDependencies": {
     "@changesets/cli": "^2.26.0",

package/test/require-photo-on-completion.test.mjs

@@ -0,0 +1,204 @@
+/*
+ * A PHOTO IS REQUIRED TO COMPLETE A TASK — and only to COMPLETE one.
+ *
+ * Owner requirement, 2026-09-10: "once task was completed they required to take
+ * photo before completing the task ... all the services that has this module
+ * must be the same process."
+ *
+ * The first version of this rule sat in the Joi schema and demanded a photo on
+ * every approve. A task in this product is a SET, not a unit: both clients tick
+ * units one at a time and open the photographs dialog on the tick that finishes
+ * the set. So that version broke every intermediate tick on both platforms —
+ * the owner hit it on the web M&E checklist, and `meareaunits.tsx` makes the
+ * same call with `attachment: []`.
+ *
+ * This exercises the SHIPPED decision function, compiled from source by the
+ * test script — not a re-typed copy.
+ */
+import test from "node:test";
+import assert from "node:assert/strict";
+import {
+  COMPLETION_PHOTO_MESSAGE,
+  readCompletion,
+  requiresCompletionPhoto,
+} from "./.build/completion-photo.util.mjs";
+
+/** Approving a unit that still has un-actioned siblings — the common tick. */
+const midSet = {
+  decision: "approve",
+  completesSet: false,
+  hasEvidence: false,
+};
+
+/** Approving the unit that finishes the set — the act evidence is for. */
+const completing = {
+  decision: "approve",
+  completesSet: true,
+  hasEvidence: false,
+};
+
+/* ── the regression the owner reported ─────────────────────────────────── */
+
+test("ticking a unit mid-set needs NO photo", () => {
+  // This is what broke: the web posts it with nothing attached, and
+  // `meareaunits.tsx` posts it with `attachment: []`.
+  assert.equal(requiresCompletionPhoto(midSet), false);
+  assert.equal(requiresCompletionPhoto({ ...midSet, attachment: [] }), false);
+  assert.equal(
+    requiresCompletionPhoto({ ...midSet, attachment: undefined }),
+    false
+  );
+});
+
+/* ── completing still requires evidence ────────────────────────────────── */
+
+test("completing the set WITHOUT a photo is refused", () => {
+  assert.equal(requiresCompletionPhoto(completing), true);
+});
+
+test("an EMPTY attachment array is not evidence", () => {
+  // The shape a client sends when its uploader failed.
+  assert.equal(
+    requiresCompletionPhoto({ ...completing, attachment: [] }),
+    true
+  );
+});
+
+test("a BLANK id is not a photo", () => {
+  assert.equal(
+    requiresCompletionPhoto({ ...completing, attachment: ["", "   "] }),
+    true
+  );
+});
+
+test("completing WITH a photo is allowed", () => {
+  assert.equal(
+    requiresCompletionPhoto({
+      ...completing,
+      attachment: ["68f05fbe0c11062938dadad9"],
+    }),
+    false
+  );
+});
+
+test("MULTIPLE photos are allowed — that is the point", () => {
+  assert.equal(
+    requiresCompletionPhoto({ ...completing, attachment: ["a1", "b2", "c3"] }),
+    false
+  );
+});
+
+/* ── the web posts a set's approves in a loop ──────────────────────────── */
+
+test("a set already carrying a photo on another unit is not blocked", () => {
+  /*
+   * `ManageChecklistMain` loops over the set's approved items and puts the ids
+   * on only ONE of them, so the approve that completes the set is not reliably
+   * the one holding the evidence. Asking only "does THIS request have a photo"
+   * would reject a set that is in fact fully documented.
+   */
+  assert.equal(
+    requiresCompletionPhoto({ ...completing, hasEvidence: true }),
+    false
+  );
+  assert.equal(
+    requiresCompletionPhoto({
+      ...completing,
+      hasEvidence: true,
+      attachment: [],
+    }),
+    false
+  );
+});
+
+/* ── rejecting must NOT be blocked ─────────────────────────────────────── */
+
+test("REJECTING is never blocked, even completing the set", () => {
+  /*
+   * A reject is the technician reporting a problem. Demanding a photograph
+   * before somebody can report one would stop them reporting it.
+   */
+  assert.equal(
+    requiresCompletionPhoto({
+      decision: "reject",
+      completesSet: true,
+      hasEvidence: false,
+    }),
+    false
+  );
+});
+
+/* ── which approve finishes the set: ONE definition with the clients ───── */
+
+test("an approve finishes the set when every other unit is approved or rejected", () => {
+  const units = [
+    { unit: "u1", approve: true, reject: false, status: "completed" },
+    { unit: "u2", approve: false, reject: true, status: "completed" },
+    { unit: "u3", approve: false, reject: false, status: "open" },
+  ];
+  assert.equal(readCompletion(units, "u3").completesSet, true);
+  // Intermediate: another unit is still untouched.
+  assert.equal(readCompletion(units, "u1").completesSet, false);
+});
+
+test("actioned means approve/reject, NOT status — status at rest is open/closed", () => {
+  /*
+   * Staging holds units that are `closed` while approved or rejected. The units
+   * list (`isFullyActioned`) and both clients count those as done, so the photo
+   * rule must too, or the server and the screen disagree about the last tick.
+   */
+  const units = [
+    { unit: "u1", approve: true, reject: false, status: "closed" },
+    { unit: "u2", approve: false, reject: false, status: "open" },
+  ];
+  assert.equal(readCompletion(units, "u2").completesSet, true);
+
+  // And a status alone, with neither flag, is not an action.
+  const statusOnly = [
+    { unit: "u1", approve: false, reject: false, status: "completed" },
+    { unit: "u2", approve: false, reject: false, status: "open" },
+  ];
+  assert.equal(readCompletion(statusOnly, "u2").completesSet, false);
+});
+
+test("a one-unit set: its only tick finishes it; an empty set finishes nothing", () => {
+  assert.equal(readCompletion([{ unit: "u1" }], "u1").completesSet, true);
+  assert.deepEqual(readCompletion([], "u1"), {
+    completesSet: false,
+    hasEvidence: false,
+  });
+});
+
+test("ids compare as strings (ObjectId vs the route param)", () => {
+  const oid = { toString: () => "68f05fbe0c11062938dadad9" };
+  const units = [
+    { unit: oid, approve: false, reject: false },
+    { unit: "u2", approve: true, reject: false },
+  ];
+  assert.equal(
+    readCompletion(units, "68f05fbe0c11062938dadad9").completesSet,
+    true
+  );
+});
+
+test("evidence counts only OTHER units' photos", () => {
+  const units = [
+    { unit: "u1", approve: false, reject: true, attachment: ["f1"] },
+    { unit: "u2", approve: false, reject: false, attachment: [] },
+  ];
+  assert.equal(readCompletion(units, "u2").hasEvidence, true);
+  assert.equal(readCompletion(units, "u1").hasEvidence, false);
+});
+
+/* ── controls ──────────────────────────────────────────────────────────── */
+
+test("CONTROL: the rule can actually say yes", () => {
+  // Without this, every assertion above could be passing against a function
+  // that returns false unconditionally.
+  assert.equal(requiresCompletionPhoto(completing), true);
+});
+
+test("CONTROL: the message names the action a person must take", () => {
+  // "Invalid payload" tells a technician standing in a plant room nothing.
+  assert.match(COMPLETION_PHOTO_MESSAGE, /take or upload at least one photo/i);
+});