@7365admin1/core 3.52.2-staging.240 → 3.52.2-staging.241

package/.changeset/plate-lookup-hides-deleted-plates.md

@@ -0,0 +1,9 @@
+---
+"@7365admin1/core": patch
+---
+
+`GET /api/people/plateNumber/:plateNumber` now hides plates whose vehicle has been deleted, like the other person reads.
+
+Its own filter is `status: { $ne: "deleted" }` on the **person**, which is unrelated to the vehicle — reading that line as "deleted plates are excluded" is why this endpoint was missed when the other two were fixed. It has no caller in the estate today, but it is routed and behind `requireAuth`, so an authenticated caller gets the resident's whole `plates[]` array back. The filter runs on read, after the cache, because whether a plate's vehicle is deleted can change inside the 15-minute TTL.
+
+`getPersonByPlateNumber` (no caller, no route) and `getApprovedPersonByPlateNumber` (a record-matching path inside `person.service.ts`, not a display path) are deliberately left alone.

package/dist/index.js

@@ -18130,7 +18130,7 @@ function usePersonRepo() {
       const cacheData = await getCache(cacheKey);
       if (cacheData) {
         import_node_server_utils41.logger.info(`Cache hit for key: ${cacheKey}`);
-        return cacheData;
+        return await withoutDeletedPlates(cacheData);
       }
       const data = await collection.find(
         { "plates.plateNumber": plateNumber, status: { $ne: "deleted" } },
@@ -18141,7 +18141,7 @@ function usePersonRepo() {
       }).catch((err) => {
         import_node_server_utils41.logger.error(`Failed to set cache for key: ${cacheKey}`, err);
       });
-      return data;
+      return await withoutDeletedPlates(data);
     } catch (error) {
       throw new import_node_server_utils41.InternalServerError("Failed to fetch people by plate number.");
     }