@7365admin1/core 3.32.2-staging.108 → 3.32.2-staging.109
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.changeset/occurrence-and-patrol-defects.md +24 -0
- package/dist/index.js +5033 -5006
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +1897 -1870
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -2
- package/test/occurrence-query.util.test.mjs +188 -0
- package/test/update-result.util.test.mjs +34 -0
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
---
|
|
2
|
+
"@7365admin1/core": patch
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Fix defects in the occurrence-book and patrol modules, and move their day
|
|
6
|
+
windows to Singapore time
|
|
7
|
+
|
|
8
|
+
- Every day window in the occurrence-book and patrol queries is now
|
|
9
|
+
Asia/Singapore (UTC+8), midnight to midnight. Computed in UTC, a day ran
|
|
10
|
+
08:00–08:00 SGT, so an entry or a patrol scan logged at 00:30 fell into the
|
|
11
|
+
previous day and the guard who made it could not find it under "today".
|
|
12
|
+
Stored data and response shapes are unchanged; only the window moves.
|
|
13
|
+
- Occurrence-book date filter returned the previous day for `DD/MM/YYYY`
|
|
14
|
+
callers, and rejected the ISO form its own validation accepts.
|
|
15
|
+
- Occurrence-book pagination was collapsed to page one whenever a date filter
|
|
16
|
+
was set, while the response still reported the full page count.
|
|
17
|
+
- Occurrence-entry search by book number could never match, because `$regex`
|
|
18
|
+
was applied to the numeric `bookEntryCount`.
|
|
19
|
+
- `PUT /api/patrol-logs/id/:id` and `PUT /api/patrol-routes/id/:id` answered
|
|
20
|
+
HTTP 200 when the update matched no document, so a failed incident-report
|
|
21
|
+
attach was reported to the user as a success.
|
|
22
|
+
- Amending an occurrence entry whose subject or signature had been deleted
|
|
23
|
+
answered HTTP 500; and deleting an already-deleted patrol route answered
|
|
24
|
+
HTTP 500 instead of succeeding.
|