@timus-networks/theme 2.4.42 → 2.4.44

package/dist/module.json

@@ -1,7 +1,7 @@
 {
   "name": "@timus-networks/theme",
   "configKey": "themeOptions",
-  "version": "2.4.42",
+  "version": "2.4.44",
   "builder": {
     "@nuxt/module-builder": "0.8.4",
     "unbuild": "2.0.0"

package/dist/module.mjs

@@ -11,7 +11,7 @@ const __filename = __cjs_url__.fileURLToPath(import.meta.url);
 const __dirname = __cjs_path__.dirname(__filename);
 const require = __cjs_mod__.createRequire(import.meta.url);
 const name = "@timus-networks/theme";
-const version = "2.4.42";
+const version = "2.4.44";
 const description = "A comprehensive Nuxt.js module providing a tailored theme experience with integrated TailwindCSS support for applications.";
 const type = "module";
 const exports = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timus-networks/theme",
-  "version": "2.4.42",
+  "version": "2.4.44",
   "description": "A comprehensive Nuxt.js module providing a tailored theme experience with integrated TailwindCSS support for applications.",
   "type": "module",
   "exports": {

package/dist/runtime/components/production/timus-breadcrumb-documentation.md

@@ -1,72 +0,0 @@
-# Path Array Documentation
-
-This document describes the `path` array, which defines routing and navigation rules for a web application.
-
-## Structure
-
-Each object in the `path` array typically contains the following properties:
-
-- `regex`: A regular expression to match URL paths
-- `label`: A text label (usually a translation key) for the path
-- `path` (optional): A redirect path or default path
-- `hidden` (optional): A boolean indicating if the path should be hidden in navigation
-- `rest`: Additional regex to match against the remaining path
-
-## Key Concepts
-
-1. **Regular Expression Matching**: The `regex` property is used to match the current route. This allows for flexible and powerful route matching.
-
-2. **Hidden Routes**: By setting `hidden: true`, you can prevent certain routes from appearing in the breadcrumb. This is useful for intermediate pages or when you want to simplify the breadcrumb trail.
-
-3. **Custom Redirects**: The `path` property allows you to specify a custom destination when a breadcrumb item is clicked. If not specified, it defaults to the matched path.
-
-4. **Rest Path Handling**: The `rest` property is an additional condition. It's used to match against the remaining path after the main `regex` match. This allows for more granular control over when a rule should apply.
-
-5. **Labeling**: The `label` property specifies the translation key for the breadcrumb text. This supports internationalization.
-
-## Usage Notes
-
-- Order matters in the `PathList`. The component will use the last matching rule it finds, so more specific rules should come later in the list.
-
-- The `regex` property can include capturing groups, which can be used to extract dynamic parts of the route (like IDs).
-
-- When using the `rest` property, the rule will only apply if both the main `regex` and the `rest` regex match.
-
-- If no matching rule is found in `PathList`, the component will automatically generate a label based on the route segments.
-
-## Examples
-
-1. **Basic Route**
-
-   ```javascript
-   {
-     regex: /^\/settings$/,
-     path: '/settings/administrators?tab=administrators',
-     label: 'header.settings.text',
-   }
-   ```
-
-   This will match the "/settings" route, display "Settings" (or its translation), and redirect to the administrators tab when clicked.
-
-2. **Hidden Route**
-
-   ```javascript
-   {
-     regex: /^\/migrations$/,
-     hidden: true,
-   }
-   ```
-
-   This will prevent the "/migrations" route from appearing in the breadcrumb.
-
-3. **Dynamic Route with Rest Condition**
-   ```javascript
-   {
-     regex: /^\/customers\/([A-Za-z0-9\-_]+)$/,
-     rest: /^subscriptions$/,
-     hidden: true,
-   }
-   ```
-   This will hide the customer ID from the breadcrumb when viewing subscriptions, resulting in a cleaner "Home > Customers > Subscriptions" breadcrumb instead of "Home > Customers > [CustomerID] > Subscriptions".
-
-By carefully crafting your `PathList`, you can create intuitive and clean breadcrumb navigation for your application.

package/dist/runtime/components/production/timus-breadcrumb.vue

@@ -1,159 +0,0 @@
-<template>
-  <div class="flex gap-4 items-center">
-    <template v-if="false">
-      <!-- Back butonu entegre etmek istersek bu v-if'i silmek işi çözer -->
-      <el-button v-if="route.path !== '/'" class="isax-arrow-left outline" size="mini" @click="goBack" />
-    </template>
-    <el-breadcrumb separator="">
-      <el-breadcrumb-item v-for="(crumb, index) in list" :key="index" v-bind="index < list.length - 1 ? { to: { path: crumb.path } } : {}">
-        {{ $t(crumb.label) }}
-        <!--{{ crumb }} Tüm Objeyi Görüntülemek İçin Bunu Kullan -->
-      </el-breadcrumb-item>
-    </el-breadcrumb>
-  </div>
-</template>
-
-<script lang="ts">
-  /**
-   * tab,id,action gibi query parametrelerini alır route'un sonuna ekler ve onları da route.path gibi gösterir.
-   * bu parametresi sadece mevcutsa eklenir. Örnek: http://localhost:3000/customers/123?tab=details
-   * bu route'da tab=details olacak ve path'i resolve ederken ['customers', '123', 'details'] şu şekilde bir listeye dikkat edecektir.
-   *
-   * `hidden` ile match eden route `hidden` olarak tanimlanabilmektedir. Mesela http://localhost:3000/customers/details/123 adresinde
-   * {regex: `^\/customers\/details$`, hidden: true} gibi bir route tanımlandığında detail ile ilgili bir route breadrump'a eklenmez. Ama öncesindeki
-   * customers ve sonrasında 123 ile ilgili tanımlar yapıldıysa onlar eklenir (yapılmadıysa otomatik ekleyecektir).
-   *
-   * `rest` olarak tanımlanmışsa, match eden route'un sonrasında kalan path'a bakar ve rest ile belirtilen regex bu path ile match
-   * ederse o zaman ister `hidden` ile gizlersiniz, isterseniz `label` ile text'ini güncellersiniz. Örneğin birbirinin benzeri 2 adet link var diyelim.
-   * http://localhost:3000/customers/123, http://localhost:3000/customers/123/subscriptions gibi. 123 ile biten route'a bir text yazdırmak isterken
-   * diğerinin 123'e ait path'ine bir şey yazdırmak istemiyor olabilirsiniz.
-   * O zaman ilk route için {regex: `^\/customers\/([A-Za-z0-9\-_]+)$`, label: 'header.customers.details.text'} tanımlarken
-   * ikincisi için {regex: `^\/customers\/([A-Za-z0-9\-_]+)$`, rest: `^\/subscriptions$`, hidden: true} demeniz yeterli olacaktır.
-   * Rest burada ikinci bir condition gibi çalışmakadır.
-   *
-   * `path` ile match eden route tıklanıldığında path ile belirtilen route'a yönlendirilir. Tanımlanmazsa kendi path'ini alacaktır.
-   *
-   *`label` ile istediğiniz match eden route'a text verebilirsiniz.
-   *
-   * Rest ile ilgili detaylı açıklama:
-   *
-   * bu `customers/1363/subscriptions` gibi bir linki resolve ederken `1363` ile ilgili bir şey yazmasına engel olacaktır.
-   * bunu yaparken regex'i match eden route'un (customers/1363) sonrasında kalan path'a bakar, `rest` ile belirtilen
-   * Regex ile uyuşuyorsa (buradaki örnekte `subscriptions`) parantez içerisinde belirtilen kısmı navigasyona eklemez.
-   * Sonuç: `customers/subscriptions` şeklinde algılar.
-   *
-   * Dilerseniz `hidden:true` ile bu route gizleyebilirsiniz. Bu durumda breadcrumbda `home > customer > subscription` gibi bir sıralama yapılacaktır.
-   * Ya da `label` ile yeni bir isim verebilirsiniz.
-   *  {
-   *    regex: /^\/customers\/([A-Za-z0-9\-_]+)$/,
-   *    rest: /^subscriptions$/,
-   *    hidden: true,
-   *  },
-   *  {
-   *    regex: /^\/customers\/([A-Za-z0-9\-_]+)$/,
-   *    rest: /^subscriptions$/,
-   *    label: "yeni isim",
-   *  },
-   */
-</script>
-
-<script setup lang="ts">
-  import { computed } from 'vue';
-  import { useRoute, useRouter } from 'vue-router';
-
-  interface Breadcrumb {
-    regex: string;
-    path: string;
-    label: string;
-    hidden?: boolean;
-    rest?: string;
-    auto?: boolean;
-    value?: string;
-  }
-
-  interface Props {
-    onChange?: Array<() => void>;
-    paths: Array<Breadcrumb>;
-  }
-
-  const props = withDefaults(defineProps<Props>(), {
-    onChange: () => [],
-    paths: () => [],
-  });
-  const route = useRoute();
-  const list = computed<Breadcrumb[]>(() => {
-    const pathArray = route.path.split('/');
-    const { tab, id } = route.query;
-    const breadcrumbs: Breadcrumb[] = [];
-    let link = '';
-
-    breadcrumbs.push({
-      path: '/',
-      label: 'header.home.text',
-      regex: '\/',
-    });
-
-    pathArray.filter(Boolean).forEach((path, index) => {
-      link += '/' + path;
-      if (index === pathArray.length - 2 && id && !tab) {
-        link += '?id=' + id;
-      }
-      const matched = findBestMatch(link);
-
-      if (matched && !matched?.hidden) {
-        breadcrumbs.push(matched);
-      }
-    });
-
-    if (tab) {
-      const matched = findBestMatch(link + '/' + tab);
-
-      if (matched && !matched?.hidden) {
-        breadcrumbs.push(matched);
-      }
-    }
-
-    return breadcrumbs;
-  });
-  const findBestMatch = (url: string): Breadcrumb | null => {
-    let bestMatch: Breadcrumb | null = null;
-    let maxMatchLength = 0;
-
-    props.paths.forEach((route: Breadcrumb) => {
-      const regex = new RegExp(route.regex);
-
-      if (regex.test(url)) {
-        const match = url.match(regex);
-
-        if (match && match[0].length > maxMatchLength) {
-          maxMatchLength = match[0].length;
-          route.path = route.path ?? match[0]; // route.path tanımsızsa match[0] ile güncelle
-
-          if (match[1]) [, route.value] = match; // match[1] mevcutsa route.value güncelle, yoksa eski değeri koru
-
-          bestMatch = route;
-        }
-      }
-    });
-
-    if (!bestMatch) {
-      let label = 'header';
-      const filteredArray = url.split('/').filter(Boolean);
-
-      filteredArray.forEach((path) => {
-        label = label + `.${path}`;
-      });
-
-      bestMatch = {
-        label: label + '.text',
-        path: url,
-        auto: true,
-        regex: '',
-      };
-    }
-
-    return bestMatch;
-  };
-  const router = useRouter();
-  const goBack = () => router.go(-1);
-</script>

package/dist/runtime/composables/useBreadcrumb.d.ts

@@ -1,6 +0,0 @@
-import type { TabsPaneContext } from 'element-plus';
-export declare function useBreadcrumb(): {
-    activeTab: import("vue").Ref<string, string>;
-    tabChanged: (tab: TabsPaneContext) => void;
-    setupBreadcrumbs: (tabs: string[]) => void;
-};

package/dist/runtime/composables/useBreadcrumb.mjs

@@ -1,42 +0,0 @@
-import { onUnmounted, ref } from "vue";
-import { useRoute, useRouter } from "#app";
-export function useBreadcrumb() {
-  const route = useRoute();
-  const router = useRouter();
-  const activeTab = ref(route.query.tab);
-  const breadcrumbTimeout = ref(null);
-  const tabList = ref([]);
-  onUnmounted(() => {
-    if (breadcrumbTimeout.value) {
-      clearTimeout(breadcrumbTimeout.value);
-    }
-  });
-  const tabChanged = (tab) => {
-    if (breadcrumbTimeout.value) {
-      clearTimeout(breadcrumbTimeout.value);
-    }
-    breadcrumbTimeout.value = setTimeout(() => {
-      router.push({
-        path: route.path,
-        query: {
-          ...route.query,
-          tab: tab.paneName,
-          page: route.query.tab !== tab.paneName ? 1 : route.query.page
-        }
-      });
-    }, 0);
-  };
-  const setActiveTab = (tab) => {
-    activeTab.value = tabList.value.includes(tab) ? tab : tabList.value[0];
-    tabChanged({ paneName: activeTab.value });
-  };
-  const setupBreadcrumbs = (tabs) => {
-    tabList.value = tabs;
-    setActiveTab(activeTab.value);
-  };
-  return {
-    activeTab,
-    tabChanged,
-    setupBreadcrumbs
-  };
-}