@7365admin1/layer-common 3.2.8-staging.214 → 3.2.8-staging.215

package/composables/useBulletinBoardPermission.ts

@@ -2,7 +2,12 @@ import { useCommonPermissions } from "./useCommonPermission";
 
 export function useBulletinBoardPermission() {
   const { hasPermission } = usePermission();
-  const { bulletinBoardPermissions: permissions } = useCommonPermissions();
+  // Same nesting rule as every other permission composable: `hasPermission`
+  // reads `catalogue[resource][action]`, and `bulletinBoardPermissions` is a
+  // flat `{action: ...}` map. Unwrapped, `catalogue["bulletin-board"]` was
+  // undefined and all five gates were reachable only through `"*"`.
+  const { bulletinBoardPermissions } = useCommonPermissions();
+  const permissions: TPermissions = { "bulletin-board": bulletinBoardPermissions };
 
   const { userAppRole } = useLocalSetup();
 

package/composables/useSettingsPermission.ts

@@ -2,7 +2,13 @@ import { useCommonPermissions } from "./useCommonPermission";
 
 export function useSettingsPermission() {
   const { hasPermission } = usePermission();
-  const { siteSettingsPermissions: permissions } = useCommonPermissions();
+  // `hasPermission` looks the action up as `catalogue[resource][action]`, so the
+  // catalogue has to be nested by resource. `siteSettingsPermissions` is a flat
+  // `{action: ...}` map, so passing it straight through made
+  // `catalogue["site-settings"]` undefined and every check below fell through to
+  // `false` -- only the `"*"` short-circuit could ever open a panel.
+  const { siteSettingsPermissions } = useCommonPermissions();
+  const permissions: TPermissions = { "site-settings": siteSettingsPermissions };
   const { userAppRole } = useLocalSetup();
 
   const canManageSiteInformation = computed(() => {

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "3.2.8-staging.214",
+  "version": "3.2.8-staging.215",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//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.",