4 Commits (33aad6a501d83881003a0911e8ed0fd440161537)

Author	SHA1	Message	Date
Debora Crescenzo	be59b85d82	MT#64377 Improve CF creation flow and Vue actions ... Introduces a new form to create a Call Forward and select its destination in a single step. Applies to Call Settings > Forwarding and Seats/Groups CF. UI: - Creation button is disabled until destination type is selected and all required fields are filled - "Number" type requires a destination number - "Custom Announcement" type requires a custom announcement - Form shows a loading state until all backend resources are created and loaded - 3 dots menus are disabled until loading is done - Destination Options list changes depending on platform type (CE/pro) and PBX feature Creation flow: 1. rewrite destination based on type and input 2. Create destination → receive ID from API 3. Create mapping using the destination ID Improvements: - Add try/catch blocks to CF actions and remove them from API file - Remove use of 'common.js' methods from CF actions - Rename 'toggleMapping' to 'setEnableMapping' - Rename 'createSpecificDestination' to 'resolveSubscriberDestination' - Update deleteMapping - Replace duplicate destinationSets, sourceSets, timeSets arrays with maps for faster lookup and single source of truth. Create relevant getters when needed. - Remove use of cloneDeep from lodash to gain better performance (shallow copies instead of deep clones) and be consistent with Vuex best practices (immutability with spread operator) Change-Id: I99ba019ac3995ddaa118f9a523f8adcd47db5a35	3 months ago
Debora Crescenzo	6f57bd1628	MT#64293 Migrate AppBadge components to Vue 3 Composition API ... - Migrate simple badge components and parent component to use <script setup> and composables pattern. - Minor CSS adjustments - Update app badge bottom spacing in `CscLayoutMain` - Simplify app badge styling in `CscPageLogin` Change-Id: I98a961ee6dc7a89e344d9387c25bdb1dc9f91f21	4 months ago
Debora Crescenzo	db5e5b55eb	MT#64292 Migrate App.Vue and vue-wait to Vue 3 ... Modernize vue-wait initialization and usage patterns to support Vue 3 Composition API while preserving Vue 2 Options API functionality. Changes: - Migrate App.vue to Vue 3 <script setup> syntax - Convert Options API to Composition API - Use defineComponent and reactive state management - Maintain existing functionality and lifecycle hooks - Refactor vue-wait initialization (boot/vue-wait.js) - Move initialization from App.vue mounted() to boot phase - Create initializeWait() function for explicit setup - Register $wait globally before component mounting - Add Vue 3 composable support (composables/useWait.js) - Create useWait() composable for Composition API components - Access $wait via getCurrentInstance() for proper Vue 3 patterns - Enable gradual migration from Options to Composition API - Update documentation (doc/architectural-overview.md) - Add "Loading State Management (vue-wait)" section - Document usage patterns for both Vue 2 and Vue 3 - Clarify migration strategy and coexistence Note: All existing Vue 2 components using this.$wait continue working unchanged while new Vue 3 components can use useWait() composable. Change-Id: I62c9eaa81336a1ae115f1b326676497dcac262b2	4 months ago
Debora Crescenzo	3f9ebb605d	MT#64044 add Vue 2/3 compatibility layer and migration infrastructure ... Add composables (useStore, useUser, usePbx, useGlobals) and pure helpers (destination, platform) to support gradual Vue 3 Composition API adoption. - Extract pure functions from mixins to src/helpers/ - Add generic store access composables in src/composables/ - Add store infrastructure helpers (RequestState, API action wrappers) - Export boot file utilities for direct import in services - Add comprehensive tests and migration documentation No breaking changes. Existing Options API code continues to work. New code can use composables and helpers for cleaner patterns. See migration-guide.md for usage examples and migration path. Change-Id: I764a5e6635771e0f95f33f86064d70ee4a746207	6 months ago