5 Commits (master)

Author	SHA1	Message	Date
Debora Crescenzo	0accdc02e8	MT#65720 Migrate ESLint config to neostandard and fix Jest ... - Replace `compat.extends('standard')` with `neostandard()`, the ESLint 9-native successor. Drop the now-unused `@stylistic/eslint-plugin` devDependency and `FlatCompat`/`@eslint/eslintrc`/`@eslint/js` imports; reuse neostandard's own bundled `@stylistic/eslint-plugin` instance under the `@stylistic` key instead, and rename `stylistic/*` rule keys to `@stylistic/*` to match. - Add an explicit `@stylistic/indent: ['error', 4]` override: the old config had `indent: 'off'` with no stylistic replacement, so plain-JS indentation was never actually linted (only Vue templates were, via `vue/html-indent`). Turning it on surfaced ~200 pre-existing drift violations across 19 files; fixed with `eslint --fix` (whitespace only, verified via `git diff -w`). - Pin `jest` to ^29.2.2 and `eslint-plugin-jest` to ^28.0.0: both had drifted to versions outside the peerDependencies range declared by @quasar/quasar-app-extension-testing-unit-jest, which is what actually wires up our test transforms. - Add `@vue/compiler-dom` as an explicit devDependency (peer of @vue/test-utils) and drop the dead `/* eslint-env node */` comment in quasar.config.js — flat config already covers it. - Drop the `form-data` yarn resolution: axios (^4.0.6) and jsdom (^4.0.6) already resolve to the patched 4.0.6 on their own, making the override from the earlier security-fix commit redundant. - Change t/testrunner to copy the checked-out source directly into /tmp (the same directory the Docker image's yarn install is run in at build time) instead of a separate /tmp/code and fix the JUnit report path to match the new working directory. - Refresh Docker image. Change-Id: I4202a718c86bedb600ce4938c1ebba77b6766ea3	6 days ago
Kirill Solomko	73858b03ff	MT#65507 migration to yarn v4 (4.17.1) ... * remove .yarn/releases/yarn-1.2.2.js * new .yarn/releases/yarn-4.17.1.cjs * migrate .yarnrc -> .yarnrc.yml * additional yarnrc.yml: * enableSripts: true (to trigger post install steps, such as binary compilation * disable telemetry * limit approvedGitRepositories to "https://npm-registry.sipwise.com/* * use classic node linker node-modules (instead of the new "pnp" one as the latter has issues with webpack) * remove debian/missing-sources/yarn-1.22.22.js * add debian/missing-sources/yarn-4.17.1.cjs * debian/rules use yarn-4.17.1.cjs * adapt Docker build for Yarn 4. Yarn 4 resolves its executable using the yarnPath configured in .yarnrc.yml. Copying the release file directly to /tmp/yarn caused Yarn to look for /tmp/.yarn/releases/yarn-4.17.1.cjs and fail. The build now preserves the expected .yarn/ structure. Change-Id: Ic65f06597022fb32777bc33179c4f242ff7bad02	1 month ago
Mykola Malkov	6767abe0fa	MT#57453 Switch docker image to bookworm ... yarnpkg is no longer available in Debian/bookworm, while we already ship a bundled yarnpkg. So use that bundled yarnpkg binary also within our Docker related actions. Also see commit bd8a150825 and MT#55813 (and related to MT#55391). Use our yarn binary as /tmp/yarn within Docker (to have to maintain it only at one place). While at it, switch Docker instructions from ADD to COPY, quoting from https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#add-or-copy -> Although ADD and COPY are functionally similar, generally speaking, COPY is preferred. Also, run pip3 install with --break-system-packages, to address new PEP 668 specific behavior of pip3, as present in Debian/bookworm: | error: externally-managed-environment | | × This environment is externally managed | ╰─> To install Python packages system-wide, try apt install | python3-xyz, where xyz is the package you are trying to | install. | | If you wish to install a non-Debian-packaged Python package, | create a virtual environment using python3 -m venv path/to/venv. | Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make | sure you have python3-full installed. | | If you wish to install a non-Debian packaged Python application, | it may be easiest to use pipx install xyz, which will manage a | virtual environment for you. Make sure you have pipx installed. | | See /usr/share/doc/python3.11/README.venv for more information. | | note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. | hint: See PEP 668 for the detailed specification. Change-Id: I09774d137925891a5f40e5597c40f48594f41d6f	3 years ago
Hans-Peter Herzog	235f0ff30c	TT#88909 Migrate Quasar to version 1.14.0 ... - Migrated external lib injection in boot files - Replaced vue-resource by axios - Applied more restrictive linting rules for Vue.js - Replaced npm by yarn - Removed old chrome release from test environment - Refactor Voicebox Settings - Refactor SpeedDial - Refactor Reminder - Refactor Call Blocking - Refactor Call Forward - Integrate jest test framework - Remove mocha test runner - Refactor User Settings - Refactor PBX Configuration - Refactor Call Change-Id: I9b2ea327e7959fb5e78d1bd53a4156ecb1c5f191	6 years ago
Hans-Peter Herzog	99bd2371fb	TT#23018 Setup: Create and prepare project skeleton for new CSC Web UI ... - Initial vue + vuex + vue-router + webpack + quasar setup - Added karma test runner - Added shrinkwrap file - Added junit reporter - Fetch subscriber - Fetch capabilities - Added Dockerfile + testrunner - Added development script for ngcp Change-Id: Ia9e58412d2b71c7e541f3d764f8fda747522c7e6	9 years ago