ngcp-csc-ui

Commit Graph

Author	SHA1	Message	Date
Giancarlo Errigo Mattos	ebafb9c5af	MT#65072 Surface real server errors instead of generic/blank messages login, loginByExchangeToken, getPreLoginPasswordInfo, getUserData, and changeExpiredPassword (src/api/user.js) assumed error bodies were JSON with a `.message` field, so a non-JSON body (e.g. nginx's HTML page for a 502/503/504) produced a blank message or a hardcoded "Unexpected error" instead of the real status/reason. Same happens with the requests behing the Dashboard page. Fix: * Add getHttpErrorMessage (src/helpers/http-error.js) to build "<status> <statusText>" from the response, falling back to a small reason-phrase table for common 5xx statuses and finally to the caller's message only when there's no response at all. Existing JSON-message behavior (Invalid OTP, Password expired, Banned, validation errors) is unchanged. * Change getList (common.js) to route errors through handleResponseError and update CscPageDashboard.vue to read reason?.message so a 502/503/504 on the dashboard's call/voicemail/device cards shows the real status instead of a generic error. Moreover, getOTPSecret/getOTPSecretAsText (src/store/user.js) had the same generic-message problem, worsened by needing the raw response (handleResponseError strips it) to tell "no OTP yet" apart from a real failure. Fix: * Rework to fetch that response directly and reuse the new helper; * Rename parseBlobToObject to parseErrorPayload/resolveBlobPayload (src/helpers/parse-error-payload.js) accordingly * fix OTP state reset timing so a blank/wrong-code retry shows "Invalid OTP Code" instead of looping back into QR discovery. Note, some requests still return the standard axios error message and will be investigated separately. Update relevant docs. Co-Authored-by: Debora Crescenzo <dcrescenzo@sipwise.com> Change-Id: Ia5a167ffdabb70fc2f604937f9472138b51172fc	2 weeks ago
Debora Crescenzo	fd5dcf0b4e	MT#64383 Migrate Dialog Components * Migrate: - CscDialog.vue - CscRemoveDialog.vue - CscRetrievePasswordDialog.vue * Add docs about remove dialog logic Change-Id: I10015ba50f2c13292fdd2cc4ca7ffe0fcb4938d5	2 months ago
Debora Crescenzo	e64887e492	MT#65003 Use composable helpers instead of direct Vuex store access - Replace direct `useStore` usage with composable helpers (useActions, useState, useGetters) - Add `setPopupShow` action to wrap `popupShow` mutation and eliminate mutations in favor of `setPopupShow` action - Remove `usePbx` and `useUser` composables - Update documentation This prepares the codebase for eventual Pinia migration by: - Avoiding mutations (Pinia has no mutations) - Centralizing store access through helpers - Enabling future migration with minimal component changes Change-Id: Iddc63b8c3c39fe1a06bb6a78ef322f01fe77a9af	3 months ago
Debora Crescenzo	a06aeb6fa7	MT#64397 Restore component names for Cypress data-cy generation e2e-testing.js automatically generates data-cy attributes for Vue components used in Cypress E2E tests. Component names were lost during the Vue 3 syntax migration, which broke automatic data-cy generation. This change restores component names so the test suite works again. Change-Id: Ia643bdf3989970243101eb7c0c275b5323a9224d	6 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	7 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	8 months ago
Debora Crescenzo	c403dc3202	MT#63999 Update Build Configuration for vue3 Resolve all build configuration conflicts and ensure all loaders and plugins are compatible. * Update eslint config to use vue3 patterns * Remove use of vuelidate/lib/validators and replace it with vue3 @vuelidate/core and @vuelidate/validators * Replace vue-wait with vue-wait-vue3 Note: we didn't touch vue-resource because unit tests are currently not in use. Change-Id: I1cf5c3b559b943307f9a4bb988f359453062a48b	9 months ago
Debora Crescenzo	1c047f546b	MT#63772 Update docs Change-Id: Idff11addcd56a2777db6815eacc34ea7bc4cc7c2	10 months ago
Debora Crescenzo	8f721d2ffc	MT#63399 Remove Obsolete Subscriber Profile Attributes Remove the following obsolete attributes from the Subscriber Profiles list in the Admin UI: - rerouting_mode - rerouting_codes - fileshare - sms Change-Id: I6074322155329ad9d9c15f65782f3ae76eac7848	12 months ago
Debora Crescenzo	2b46170467	MT#63356 Align CSC route guards with menu visibility - Verify and correct route access for admin-only CSC pages - Update route guard logic to support: * User role (admin / non-admin) * Exact match on user profile attribute * Presence of one or more profile attributes * Required licenses (all must exist) * Exact platfom feature * Exact capability match - Ensure route guards match menu visibility restrictions - Document route guards and menu visibility logic - Note: for fax settings, we use the extra variable `isFaxServerSettingsActive` to determine whether the toggle in the fax server menu should be on or off. Change-Id: Id60a0e8b2145701ed4ae52d0859da46172076a89	1 year ago
Hans-Peter Herzog	beef3b3ebb	TT#96253 Upgrade to Quasar 1.14.1 - Update Vue.js component docs Change-Id: I96596a66d0a5f32b091ca37cde1b53de85c52d1e	6 years ago
Hans-Peter Herzog	db22ffebb1	TT#96150 Improve developer guide Change-Id: Ifdc81fe263cf953e52bbf876bf89dd7aafbf2f54	6 years ago
Hans-Peter Herzog	b47c7e6061	TT#95950 Introduce a basic pattern to create and handle Dialogs Change-Id: I23fa5786ced7cf66ba59256c356b7b556387388f	6 years ago

13 Commits (master)