@7365admin1/layer-common 4.90.2-staging.491 → 4.90.3

package/components/AppSelect.vue

@@ -18,8 +18,7 @@
 <template>
   <v-menu
     v-if="!multiple"
-    v-model="singleOpen"
-    :close-on-content-click="!searchable"
+    :close-on-content-click="true"
     :disabled="disabled"
     location="bottom start"
     offset="4"
@@ -53,27 +52,9 @@
       </div>
     </template>
 
-    <div
-      ref="singleMenu"
-      class="app-select__menu"
-      role="listbox"
-      @scroll.passive="onMenuScroll"
-    >
-      <div v-if="searchable" class="app-select__search">
-        <v-icon icon="mdi-magnify" size="16" />
-        <input
-          ref="singleSearchInput"
-          v-model="search"
-          type="text"
-          class="app-select__search-input"
-          :placeholder="searchPlaceholder"
-          aria-label="Search options"
-          @keydown.enter.prevent="selectFirstMatch"
-          @keydown.esc.stop="singleOpen = false"
-        >
-      </div>
+    <div class="app-select__menu" role="listbox">
       <button
-        v-for="opt in visibleOptions"
+        v-for="opt in normalized"
         :key="String(opt.value)"
         type="button"
         class="app-select__option"
@@ -85,14 +66,6 @@
         <span class="app-select__option-text">{{ opt.title }}</span>
         <v-icon v-if="isSingleOn(opt)" icon="mdi-check" size="17" />
       </button>
-      <p v-if="searchable && !visibleOptions.length" class="app-select__empty">
-        {{ normalized.length ? "No matches" : "Nothing to choose from" }}
-      </p>
-      <!-- In the list, not under the field: the wait belongs where the reader's
-           eye already is, at the end of what they just scrolled through. -->
-      <p v-if="loadingMore" class="app-select__loading" role="status">
-        Loading more...
-      </p>
     </div>
   </v-menu>
 
@@ -149,18 +122,8 @@
     </template>
 
     <div class="app-select__menu">
-      <div v-if="searchable" class="app-select__search">
-        <v-icon icon="mdi-magnify" size="16" />
-        <input
-          v-model="search"
-          type="text"
-          class="app-select__search-input"
-          :placeholder="searchPlaceholder"
-          aria-label="Search options"
-        >
-      </div>
       <button
-        v-for="opt in visibleOptions"
+        v-for="opt in normalized"
         :key="String(opt.value)"
         type="button"
         class="app-select__option"
@@ -175,9 +138,6 @@
         />
         <span class="app-select__option-text">{{ opt.title }}</span>
       </button>
-      <p v-if="searchable && !visibleOptions.length" class="app-select__empty">
-        {{ normalized.length ? "No matches" : "Nothing to choose from" }}
-      </p>
     </div>
   </v-menu>
 </template>
@@ -194,34 +154,6 @@ defineOptions({ inheritAttrs: false });
  */
 const model = defineModel<any>({ default: "" });
 
-/**
- * ASKING FOR THE NEXT PAGE, FROM INSIDE THE LIST.
- *
- * A dropdown that pages should load as it is scrolled - a button under the
- * field asks the reader to leave the list they are reading to fetch more of it.
- * The menu is already the scroll container (`max-height: 280px; overflow-y:
- * auto` in `primitives.css`), so the end of the list is the natural trigger.
- */
-const emit = defineEmits<{ (e: "load-more"): void }>();
-
-/** How close to the end counts as the end. About one row and a half. */
-const LOAD_MORE_SLACK_PX = 48;
-
-const singleMenu = ref<HTMLElement | null>(null);
-/* Scroll fires per pixel. This makes the ask happen once per ARRIVAL at the
-   end, not once per event, and rearms when the list grows under the reader. */
-const askedAtBottom = ref(false);
-
-function onMenuScroll(event: Event) {
-  const el = event.target as HTMLElement | null;
-  if (!el || !props.hasMore || props.loadingMore) return;
-  const near = el.scrollHeight - el.scrollTop - el.clientHeight <= LOAD_MORE_SLACK_PX;
-  if (near && !askedAtBottom.value) emit("load-more");
-  askedAtBottom.value = near;
-}
-
-
-
 const props = defineProps({
   label: { type: String, default: "" },
   /** Strings, or the `{ title, value }` shape `v-select` already takes. */
@@ -236,22 +168,6 @@ const props = defineProps({
   returnObject: { type: Boolean, default: false },
   clearable: { type: Boolean, default: false },
   placeholder: { type: String, default: "" },
-  /**
-   * A filter box at the top of the popover. Opt-in, so the 44 consumers that
-   * do not ask for it render exactly the DOM they render today - a list short
-   * enough to read does not want a search field in front of it.
-   */
-  searchable: { type: Boolean, default: false },
-  /**
-   * MORE OPTIONS EXIST THAN ARE LOADED - see the `load-more` emit.
-   *
-   * Opt-in, and single-select only for now. A caller that leaves these alone
-   * behaves exactly as it did: no footer, no listener, no emit.
-   */
-  hasMore: { type: Boolean, default: false },
-  /** A page is on its way; shows the footer and stops further asking. */
-  loadingMore: { type: Boolean, default: false },
-  searchPlaceholder: { type: String, default: "Search" },
 });
 
 const normalized = computed(() =>
@@ -262,56 +178,6 @@ const normalized = computed(() =>
   )
 );
 
-/* ---- search ---------------------------------------------------------- */
-
-const search = ref("");
-const singleOpen = ref(false);
-const singleSearchInput = ref<HTMLInputElement | null>(null);
-
-/* Case-insensitive substring over what the option READS AS, not its value:
-   the title is the only part the user can see to type. */
-const visibleOptions = computed(() => {
-  const term = search.value.trim().toLowerCase();
-  if (!props.searchable || !term) return normalized.value;
-  return normalized.value.filter((opt) =>
-    String(opt.title ?? "").toLowerCase().includes(term)
-  );
-});
-
-/*
- * A page that does not fill the menu leaves nothing to scroll, and the reader
- * would be stranded with no way to reach the rest. That is not hypothetical
- * here: a page of ten whose rows are mostly filtered out by the caller can draw
- * four options in a box built for eight. So whenever the list settles short of
- * its own container, the next page is asked for straight away.
- */
-watch(
-  () => [visibleOptions.value.length, props.hasMore, props.loadingMore, singleOpen.value],
-  async () => {
-    if (!props.hasMore || props.loadingMore || !singleOpen.value) return;
-    await nextTick();
-    const el = singleMenu.value;
-    if (el && el.scrollHeight <= el.clientHeight) emit("load-more");
-  },
-  { flush: "post" },
-);
-
-/* A stale term would hide the list the next time the popover opens, so it is
-   dropped on every open - and the caret goes into the box, since opening a
-   searchable select is almost always a prelude to typing. */
-watch(singleOpen, async (open) => {
-  if (!props.searchable) return;
-  search.value = "";
-  if (!open) return;
-  await nextTick();
-  singleSearchInput.value?.focus();
-});
-
-function selectFirstMatch() {
-  const [first] = visibleOptions.value;
-  if (first) selectSingle(first);
-}
-
 /* A model entry is either the plain value or - under `return-object` - the
    source item, so everything compares on this one key. */
 const keyOf = (v: any) =>
@@ -339,11 +205,6 @@ const isSingleOn = (opt: any) =>
 function selectSingle(opt: any) {
   if (props.disabled) return;
   model.value = props.returnObject ? opt.raw : String(opt.value);
-  // `close-on-content-click` has to be OFF while searching - it fires on the
-  // click that puts the caret in the search box, so the popover would shut the
-  // moment it was typed into. With it off, picking an option has to close the
-  // popover by hand.
-  if (props.searchable) singleOpen.value = false;
 }
 
 function clearSingle() {

package/components/BuildingUnitFormEdit.vue

@@ -10,7 +10,6 @@
         <v-tab value="general">General</v-tab>
         <v-tab value="residents">Residents/Tenants</v-tab>
         <v-tab value="vehicles">Vehicles</v-tab>
-        <v-tab value="management">Management</v-tab>
         <v-tab value="others">Others</v-tab>
       </v-tabs>
     </v-toolbar>
@@ -171,11 +170,6 @@
         </TableMain>
       </template>
 
-      <template v-else-if="tab === 'management'">
-        <BuildingUnitManagement :unit-id="buildingUnit._id" :site-id="buildingUnit?.site?._id"
-          :can-update="canUpdateUnit" />
-      </template>
-
       <template v-else-if="tab === 'others'">
         <v-row>
           <!-- <v-col cols="12" md="6" class="mt-2">

package/components/Dialog/UpdateMoreAction.vue

@@ -23,7 +23,7 @@
         Close
       </v-btn>
 
-      <v-menu v-if="canUpdate || canDelete || $slots.actions" contained>
+      <v-menu v-if="canUpdate || canDelete" contained>
         <template #activator="{ props }">
           <v-btn
             variant="flat"
@@ -42,16 +42,6 @@
              render-verified either. Only the row type and the destructive ink
              change. -->
         <v-list class="pa-0 update-more__list">
-          <!--
-            Screen-specific rows, above Edit and the destructive one.
-
-            Additive: a screen that passes nothing gets the menu it always
-            had, and `$slots.actions` is undefined unless a caller actually
-            defines the slot - so the button does not appear over an empty
-            list when a screen has neither permission nor extra rows.
-          -->
-          <slot name="actions" />
-
           <v-list-item v-if="canUpdate" @click="emit('edit')">
             <v-list-item-title>
               {{ editButtonLabel }}