@7365admin1/layer-common 4.0.3-staging.231 → 4.0.3-staging.232

package/components/CreateSubsciptionPlan.vue

@@ -5,9 +5,16 @@
       {{ isEditing ? "Edit Plan" : "Create New Plan" }}
     </v-card-title>
 
-    <!-- Form Content -->
-    <v-form ref="formRef" @submit.prevent="submit">
-      <v-card-text class="screen-modal__body px-6 pt-4">
+    <!--
+      Form Content. The FORM sits INSIDE the body, not around it. The body is
+      what scrolls; a `v-form` wrapped around body + footer is an unshrinkable
+      flex item, so a long applications list pushed the footer past the card's
+      capped height and Save became unreachable. Same shape as
+      `AccessCardAddForm`. Submit is fired from the footer button by hand
+      because the button now lives outside the form element.
+    -->
+    <v-card-text class="screen-modal__body px-6 pt-4">
+      <v-form ref="formRef" @submit.prevent="submit">
         <!-- Plan Details Section -->
         <div class="plan-form__section">Plan Details</div>
 
@@ -196,24 +203,24 @@
         >
           {{ errors.pricing }}
         </v-alert>
-      </v-card-text>
-
-      <!-- Footer Buttons -->
-      <v-card-actions class="screen-modal__footer">
-        <v-row no-gutters>
-          <v-col cols="6" class="pr-2">
-            <v-btn block variant="outlined" class="text-none screen-btn-ghost" @click="$emit('cancel')">
-              Cancel
-            </v-btn>
-          </v-col>
-          <v-col cols="6" class="pl-2">
-            <v-btn block type="submit" variant="flat" class="text-none screen-btn-primary">
-              {{ isEditing ? "Save Changes" : "Create Plan" }}
-            </v-btn>
-          </v-col>
-        </v-row>
-      </v-card-actions>
-    </v-form>
+      </v-form>
+    </v-card-text>
+
+    <!-- Footer Buttons -->
+    <v-card-actions class="screen-modal__footer">
+      <v-row no-gutters>
+        <v-col cols="6" class="pr-2">
+          <v-btn block variant="outlined" class="text-none screen-btn-ghost" @click="$emit('cancel')">
+            Cancel
+          </v-btn>
+        </v-col>
+        <v-col cols="6" class="pl-2">
+          <v-btn block variant="flat" class="text-none screen-btn-primary" @click="submit">
+            {{ isEditing ? "Save Changes" : "Create Plan" }}
+          </v-btn>
+        </v-col>
+      </v-row>
+    </v-card-actions>
   </v-card>
 </template>
 

package/components/SubscriptionPlanTable.vue

@@ -181,15 +181,20 @@
       </v-data-table>
     </AppCard>
 
-    <!-- Create / Edit Dialog -->
+    <!--
+      Create / Edit Dialog. The form component renders its OWN `.screen-modal`
+      card, so it has to be the dialog's DIRECT child: Vuetify only makes
+      `.v-overlay__content > .v-card` a capped flex column. Wrapping it in a
+      second `v-card` handed that treatment to the wrapper and left the real
+      card a plain `overflow: hidden` block - it grew past the viewport and
+      clipped its own Cancel/Save footer, with no scrollbar to reach it.
+    -->
     <v-dialog v-model="showModal" max-width="600px" persistent>
-      <v-card class="pa-4">
-        <CreateSubscriptionPlan
-          :initial-plan="editingPlan"
-          @cancel="closeModal"
-          @submit="handleSubmit"
-        />
-      </v-card>
+      <CreateSubscriptionPlan
+        :initial-plan="editingPlan"
+        @cancel="closeModal"
+        @submit="handleSubmit"
+      />
     </v-dialog>
 
     <Snackbar v-model="messageSnackbar" :text="message" :color="messageColor" />

package/package.json

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