@7365admin1/layer-common 4.2.5-staging.272 → 4.2.6
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/CHANGELOG.md +25 -4
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,26 @@
|
|
|
1
1
|
# @iservice365/layer-common
|
|
2
2
|
|
|
3
|
+
## 4.2.6
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- a7631fe: Remove stray debug `console.log` calls from shipped components, composables, middleware and plugins, and move the ones on failure paths to `console.error`. No behaviour change.
|
|
8
|
+
|
|
9
|
+
## 4.2.5
|
|
10
|
+
|
|
11
|
+
### Patch Changes
|
|
12
|
+
|
|
13
|
+
- 7a6cc0f: Vehicle form: name a block/level/unit the picker cannot offer, instead of showing its id.
|
|
14
|
+
|
|
15
|
+
The Season Pass edit dialog fetches its record with a plain findOne, so block,
|
|
16
|
+
level and unit arrive as raw ids. The vehicle LIST already resolves those names
|
|
17
|
+
server-side, so the list row's names are handed down to the dialog. A value that
|
|
18
|
+
is no longer selectable now reads "Tower Ten (no longer selectable)"; a value no
|
|
19
|
+
name exists for reads a plain sentence and logs the id for support. A Mongo id
|
|
20
|
+
is never rendered. The stored value is untouched.
|
|
21
|
+
|
|
22
|
+
- bc4355f: Vehicle form: closing the "Matching Records" picker with the header X no longer clears a Unit the user had already chosen. Block / Level / Unit no longer render a raw Mongo ObjectId when the id is not in the site's list — a deleted building unit now says so instead. Also removes a stray `console.log` from the bulletin board form that shipped to the browser on every render.
|
|
23
|
+
|
|
3
24
|
## 4.2.4
|
|
4
25
|
|
|
5
26
|
### Patch Changes
|
|
@@ -492,11 +513,11 @@
|
|
|
492
513
|
`utils/console-tier.ts` + `composables/useConsoleTier.ts` mirror the server's
|
|
493
514
|
own rule from two endpoints the console already calls, unprojected:
|
|
494
515
|
|
|
495
|
-
|
|
496
|
-
|
|
516
|
+
GET /api/members/user/:user/app/admin the Seven365 staff membership
|
|
517
|
+
GET /api/roles/id/:role that membership's role document
|
|
497
518
|
|
|
498
|
-
|
|
499
|
-
|
|
519
|
+
owner = member.type === "admin" && role.type === "admin" && role.default === true
|
|
520
|
+
staff = member.type === "admin" && role.type === "admin"
|
|
500
521
|
|
|
501
522
|
`role.default` is the marker because it is the only property of a platform
|
|
502
523
|
staff role no API caller can set - `role.controller.ts` validates create and
|
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "@7365admin1/layer-common",
|
|
3
3
|
"license": "MIT",
|
|
4
4
|
"type": "module",
|
|
5
|
-
"version": "4.2.
|
|
5
|
+
"version": "4.2.6",
|
|
6
6
|
"author": "7365admin1",
|
|
7
7
|
"main": "./nuxt.config.ts",
|
|
8
8
|
"//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.",
|