@dsivd/prestations-ng 19.0.2-beta.6 → 19.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -5,9 +5,12 @@ Back offices that are behind IAM ACV should migrate to OIDC, IAM headers are now
5
5
  ## ADMIN
6
6
 
7
7
  - You have to request a new VIP for your application (<env>-<deployunit>.etat-de-vaud.ch)
8
- - i.e. for sesamebo (R260429_00018) : https://int-sesame.etat-de-vaud.ch/
9
- - On IAM side, you have to request a client id / secret on every environment to be used in your configuration
8
+ - i.e. for sesamebo (R260429_00018, R260810_00031 for eldoradobo prod) : https://int-sesame.etat-de-vaud.ch/
9
+ - Pay attention that they won't be able to finish the task if no pod has been started, so you need
10
+ to synchronize the guys, especially for production
11
+ - On IAM side, you have to request a client id / secret on every environment
10
12
  - i.e. for sesamebo (S260429_00110)
13
+ - PUT it in your configuration before releasing, i.e. https://dsigit.etat-de-vaud.ch/outils/git/projects/CYBER/repos/configuration-bo/browse/eldoradobo-PR.properties#28
11
14
 
12
15
  ## FRONTEND
13
16
 
package/UPGRADING_V17.md CHANGED
@@ -151,7 +151,7 @@ Add `/.nx/cache`
151
151
  ```bash
152
152
  npm install @angular/cli@17 -g
153
153
  ng update @angular/core@17 @angular/cli@17 --force
154
- ng update @dsivd/prestations-ng@latest
154
+ ng update @dsivd/prestations-ng@17
155
155
  ng update rxjs@7
156
156
  ng update @angular-eslint/builder@17
157
157
  ng update @angular-eslint/eslint-plugin@17 @angular-eslint/eslint-plugin-template@17 @angular-eslint/template-parser@17
@@ -167,6 +167,11 @@ npm install puppeteer@~23.5.2 --save-dev
167
167
  npm update
168
168
  ```
169
169
 
170
+ If you go errors like "npm error code ERESOLVE
171
+ npm error ERESOLVE could not resolve
172
+ " while executing `npm remove puppeteer`, you can run :
173
+ `npm i primeng@^17 primeicons@^7 @angular/cdk@^17 @angular/material@^17` to align versions first.
174
+
170
175
  #### Align Angular & ESLint versions
171
176
 
172
177
  Make sure that @angular & @angular-eslint packages are aligned up to the minor version (17.X).
package/UPGRADING_V18.md CHANGED
@@ -456,8 +456,9 @@ Just FYI if you are curious about the details, you can find the Angular update g
456
456
  ```bash
457
457
  npm install @angular/cli@19 -g
458
458
  ng update typescript@5.5
459
- ng update @dsivd/prestations-ng@latest
459
+ ng update @dsivd/prestations-ng@18
460
460
  ```
461
+ NB: You might need to use the --force option.
461
462
 
462
463
  When asked the question "Select the migrations that you'd like to run", accept "provide-initializer" by hitting "Space" key then "Enter".
463
464
 
package/UPGRADING_V19.md CHANGED
@@ -292,6 +292,8 @@ When a unique identifier such as `id` is not possible, track by object or as a l
292
292
  ng update @angular/cdk@20
293
293
  ```
294
294
 
295
+ NB: you might need to use the `--force` option
296
+
295
297
  ### Running with node 22+
296
298
 
297
299
  #### In your project
@@ -314,6 +316,8 @@ Update your `package.json` file to specify the node engine:
314
316
 
315
317
  ```diff
316
318
  buildAppPipelinePodmanUT([
319
+ - jdk: 21,
320
+ + jdk: 25,
317
321
  - node: 20,
318
322
  + node: 22,
319
323
  ])
@@ -361,6 +365,8 @@ ng update @angular/cdk@21
361
365
  ng update ngx-matomo-client@9
362
366
  ```
363
367
 
368
+ 💡 **NB: Upgrade all other libraries needed by your project (such as: primeng, lodash, ...) to their latest version compatible with angular 21**
369
+
364
370
  ### Quick fix
365
371
 
366
372
  - In all custom components extending `FoehnInputComponent`, in `providers` providing `FoehnInputComponent` remove `multi: true,`.
@@ -577,7 +583,7 @@ ng generate @angular/core:route-lazy-loading
577
583
 
578
584
  Here is an example when doing it manually because schematic above does not work as intended:
579
585
 
580
- Your `app.routing.ts` file should look something like this:
586
+ Your `app.routes.ts` file should look something like this:
581
587
 
582
588
  ```ts
583
589
  const routes: Routes = [
@@ -1398,18 +1404,21 @@ You should see in your project root folder `.husky` a new folder `_`.
1398
1404
 
1399
1405
  #### lint-staged
1400
1406
 
1401
- In your `package.json` file, check for existing `lint-staged` section and add/modify with the following content. If it does not exist, create it:
1407
+ In your `package.json` file, check for existing `lint-staged` section and add/modify with the `"lint-staged"` section in the following content. If it does not exist, create it:
1402
1408
 
1403
1409
  ```json
1404
- "lint-staged": {
1405
- "*.ts": [
1406
- "eslint --fix",
1407
- "prettier --config ./.prettierrc --write"
1408
- ],
1409
- "*.{js,jsx,json,css,scss,md,html}": [
1410
- "prettier --config ./.prettierrc --write"
1411
- ]
1412
- },
1410
+ {
1411
+ "scripts": {...},
1412
+ "lint-staged": {
1413
+ "*.ts": [
1414
+ "eslint --fix",
1415
+ "prettier --config ./.prettierrc --write"
1416
+ ],
1417
+ "*.{js,jsx,json,css,scss,md,html}": [
1418
+ "prettier --config ./.prettierrc --write"
1419
+ ]
1420
+ }
1421
+ }
1413
1422
  ```
1414
1423
 
1415
1424
  #### Manually run formatting commands
Binary file