@7365admin1/layer-common 4.2.1-staging.258 → 4.2.1-staging.259

package/components/InvitationForm.vue

@@ -160,6 +160,15 @@ const props = defineProps({
     type: String,
     default: "",
   },
+  /*
+   * Pre-bind the invitation to one site.
+   *
+   * This prop has been declared since the component was written and was never
+   * read anywhere - `invite.site` was only ever filled by the Site picker. A
+   * caller that already knows the site (onboarding step 6, "Invite Site Admin",
+   * which is about the site created in step 4) had no way to say so. It is
+   * wired to `invite` below.
+   */
   site: {
     type: Object as PropType<TCustomerSite>,
     default: () => ({
@@ -225,17 +234,34 @@ watch(
   () => {
     invite.value.org = props.org || ""
 
-    if (props.hideApp) {
-      invite.value.app = "property_management_agency"
-      return
-    }
-
+    /*
+     * `hideApp` HIDES the App field (see the `v-if` in the template). It also
+     * used to overwrite the value with a literal "property_management_agency",
+     * so a caller that hid the field could not choose what it was hiding, and
+     * every organisation - security, cleaning, landscaping - was invited into
+     * property management. Hiding a field is not the same as deciding it.
+     *
+     * `adminState: false` keeps its existing fallback: that flag is about the
+     * ORGANISATION-admin invitation, which is a separate flow, and changing it
+     * here would move where those members land.
+     */
     invite.value.app = props.adminState
       ? (props.app || "")
       : "property_management_agency"
   },
   { immediate: true }
 )
+
+/* A caller-supplied site wins; the picker still works when there is none. */
+watch(
+  () => props.site,
+  (site) => {
+    if (!site?.site) return
+    invite.value.site = site.site
+    invite.value.siteName = site.name || ""
+  },
+  { immediate: true, deep: true }
+)
 // invite.value.app = props.app;
 // invite.value.org = props.org ?? "";
 

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.2.1-staging.258",
+  "version": "4.2.1-staging.259",
   "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.",