This update introduced many breaking changes.
Listed here the most important ones:
* quasar.conf.js file has been renamed
quasar.config.js.
* Quasar v4 replaced the old /src/index.template.html
with a new /index.html at the root of the project.
The special comment <!-- quasar:entry-point -->
is used to inject scripts/styles automatically.
* Use setupMiddlewares instead of onBeforeSetupMiddleware.
* proxy is now an array of proxy config objects.
* Dropped support for Vuex. We can still use Vuex as any
Vue plugin, but we have to manage everything (installing the
store, no store parameter in boot files, etc.).
We'll migrate to Pinia asap.
* Updated postcssrc according to docs
Change-Id: I585a3e2d17f666d9ca2773fa446d644f0fc201a2
(cherry picked from commit 72d36d22ab)
(cherry picked from commit b70ea928dd)
* Run yarn outdated and run through the list
to upgrade all libs but @quasar/app-webpack
and related libs. this will be done in a
separate commit.
* Remove parseuri because it is not used anywhere
in fact the project has a custom SIP URI parsing
implementation in sip-uri-parse.js.
* Remove jwt-decode because it is not used in fact
JWT decoding is manually implemented using native
browser functions.
* Updating to glob@11 where the glob.sync() method
is no longer accessible, but requires to be
imported directly from globModule.
* Remove eventsource:
- No Direct Usage: I could not find any direct imports,
requires, or uses of the eventsource package or
EventSource APIs in the codebase.
- Security Updates: The package was updated on
January 11, 2023, from version 1.1.1 to 2.0.2 as
part of a security updates (MT#56339).
- No Indirect Dependencies: The yarn why eventsource
command confirmed that no other packages depend on
eventsource.
- No Build Process Integration: I didn't find any
references to eventsource in the build config files
or webpack configurations.
- No SSE Implementation: While we handle media streams
for calls, in my understanding they use WebRTC or
similar technologies, not Server-Sent Events which,
in my understanding, is what eventsource is designed
for.
* Remove eslint-plugin-standard as it's not longer needed
by standard and eslint-config-standard.
* Upgrading eslint-plugin-vue required adding
vue-eslint-parser as a peer dependency and
required some changes to since new warnings.
Change-Id: I8f582275ae344f0ede7520136deba30c4d94ffd7
(cherry picked from commit bc75777bae)
(cherry picked from commit e896edfb38)
Migrating from ^8.10.0 to 9.14.0 had breaking changes.
* We moved to a flat configuration and changed the amended the script to run lint.
* We upgraded all eslint relevant libraries/plugins.
* We opened another ticket to review all the console.log/debug/info present in the repo.
Change-Id: Ie1e2c1ef49fc09cddbd9cc639505a1a65917bd35
(cherry picked from commit e935071c95)
(cherry picked from commit 7f207e4462)
Bump axios from previous version to 1.13.1 for security and stability improvements
Change-Id: I3855f02d71837f0b6c7e86590f6b8e5ab16d2cb4
(cherry picked from commit 3a6f992f4a)
(cherry picked from commit a779465321)
Remove stylus library as it has a malware
and it is not used in the repo.
We are not backporting the trunk commit
as currently the two branches have huge
differences with regards of libs versions.
NGCP-Flow:mr12.5
Change-Id: I9820133e59cf01a3c55a446ec94d1e55c8c1ed49
(cherry picked from commit 37b0c94920)
Manually backport dependencies upgrade
commit:
09f639c935
because we don't want to upgrade eslint
on mr12.5
NGCP-Flow: mr12.5
Change-Id: Ib52e73ed589283e55bc406a27c827e4d9299515f
(cherry picked from commit 87bb081659)
To clean up a bit the situation we upgrade all possible
dependencies to resolve vulnerabilities alerts and
adapt the code where necessary.
* Started with 89 vulnerabilities.
Severity: 13 Low, 44 Moderate,32 High
* Result: 1 vulnerability.
Severity: 1 Moderate
Change-Id: Ic0d9f1aa7c05ea5cb01980e8e110260b4f5dc534
(cherry picked from commit 3d0180e9e6)
(cherry picked from commit 486e23a18b)
We run the npx command to update to the latest version
Change-Id: I53a746bad93e73a53ea127294f8e026f3301e0e8
(cherry picked from commit 7c9a494897)
(cherry picked from commit 86d4ea1a88)
- remove some spaces and some code in comment
- change icon for upload
- adding an error for the number when it is duplicated in add/edit pages
Change-Id: I3f1ca01e70a1b3bcf068bdea3c5cc98668f74c9f
The jest module cannot be found after the update due
to a wrong transformation:
07:46:39 yarn run v1.22.19
07:46:39 $ jest --updateSnapshot
07:46:39 ● Validation Error:
07:46:39
07:46:39 Module vue-jest in the transform option was not found.
07:46:39 <rootDir> is: /tmp/code
07:46:39
07:46:39 Configuration Documentation:
07:46:39 https://jestjs.io/docs/configuration
This commit fixes the transformation and points to the new
'@vue/vue3-jest'
Change-Id: If781a23155352d0e3275c064bbca92d17076dbad
- Enable and disable camera during the call
- Enable and disable screen during the call
- Switch from camera to screen and back
- Send in-band DTMF
- Send "603 Decline" on termination
Change-Id: Ife56ca49cadade44ee9b70b77b3f345b262be9d9
Note: to test it you can add some JS code with translations in commented block. That translation should not apper in en.json file if you execute "yarn run i18n:extract" command
Change-Id: I79f6a8358f3a52578b58044eb02169aaccf62123
- TT#128156 Add QR-Code button to the header
- TT#128157 Add QR-Code render library
- TT#128158 Implement QR-Code generation
- TT#129205 Render QR-Code in the popup
- TT#129224 Create store test and api test (including endpoint mockup)
NOTE
You need to enable sip_phone.show_qr_csc in /etc/ngcp-config/config.yml of your environment to be able to see the QR code icon
Change-Id: Ifa065ef057549696387026c5a62cf0f5297ffb05
AC:
Can run a script from package.json "i18n:extract" to add new translation keys found in source files
Can see the new translation in all language files
Can see an empty string but the key for untranslated phrases
Can see all language files synchronised based on the english translation
Change-Id: I7181a5224836f5e8f275cee4c975cb6d5199d8c0
AC:
Can add forwarding
Can alter forwarding
Can remove forwarding
Can enable forwarding
Can disable forwarding
Can enable that primary number rings
Can disable that primary number rings
Can forward to Number
Can forward to Voicebox
Can forward to Fax2Mail
Can forward to ManagerSecretary
Can forward to Conference
Can create SourceSet
Can assign number to SourceSet
Can remove number from SourceSet
Can change name of the SourceSet
Can search for existing SourceSets
Can assign an existing SourceSet
Can assign TimeSet (Date)
Can delete TimeSet (Date)
Can assign TimeSet (Date range)
Can delete TimeSet (Date range)
Can assign TimeSet (Weekdays)
Can delete TimeSet (Weekdays)
Can assign TimeSet (Office Hours)
Can delete TimeSet (Office Hours)
Change-Id: If5e5267e229a20947e0278212f59349d9e2eb7be
AC:
Can manage loading states without implementing boilerplate store code
Can use the Vue.$wait plugin in the context of a vue component
Can start a loading context with $wait.start('loading-context')
Can check the loading state of a context with $wait.is('loading-context')
Can end a loading context with $wait.end('loading-context')
Sources:
https://github.com/f/vue-wait
Change-Id: I4318729e5193bc362b4f13186d3f2f16dac90e8b
The Quasar Framework has released a new PATCH Version 1.14.3 and we intend to upgrade it by using "quasar upgrade" and "quasar upgrade -i".
Not only the quasar package, but also the Extras and the QuasarApp package are going to be upgraded.
Change-Id: I668209bdc09586b60cf5a78451b51b0f1045a449
This change fixes dependencies according to the audit report, that was created by "yarn audit".
The issues where fixed by using "yarn-audit-fix --package-lock-only"
Change-Id: I460637353254b0186e6348b4407d2dcdeb6982b0