@7365admin1/core 3.62.1-staging.278 → 3.62.1-staging.279
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/role-module-ceiling.md +16 -0
- package/dist/index.js +5102 -5014
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +178 -90
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
- package/test/site-modules.test.mjs +151 -0
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
"@7365admin1/core": minor
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Enforce the organisation's module ceiling on every role write (R1 tier three).
|
|
6
|
+
|
|
7
|
+
A role can no longer be granted a permission whose module Seven365 never gave
|
|
8
|
+
the organisation, nor one the organisation never gave the site. Applied to all
|
|
9
|
+
four write paths — `role.controller` create / update / updatePermissionsById and
|
|
10
|
+
`role-v2.controller` create — because `/api/roles/v2` is a separate mount and
|
|
11
|
+
gating one leaves the rule reachable by adding `/v2` to the URL.
|
|
12
|
+
|
|
13
|
+
Only what a write ADDS is tested, so a role that predates the module list can
|
|
14
|
+
still be renamed and can still have a permission removed. Absent and empty
|
|
15
|
+
module lists still mean everything at every tier, so this is inert for all 168
|
|
16
|
+
live organisations until Seven365 sets a list.
|