@dsivd/prestations-ng 19.0.2 → 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_V19.md CHANGED
@@ -291,7 +291,8 @@ When a unique identifier such as `id` is not possible, track by object or as a l
291
291
  ```bash
292
292
  ng update @angular/cdk@20
293
293
  ```
294
- NB: you might need to use the `--force` option
294
+
295
+ NB: you might need to use the `--force` option
295
296
 
296
297
  ### Running with node 22+
297
298
 
@@ -364,6 +365,8 @@ ng update @angular/cdk@21
364
365
  ng update ngx-matomo-client@9
365
366
  ```
366
367
 
368
+ 💡 **NB: Upgrade all other libraries needed by your project (such as: primeng, lodash, ...) to their latest version compatible with angular 21**
369
+
367
370
  ### Quick fix
368
371
 
369
372
  - In all custom components extending `FoehnInputComponent`, in `providers` providing `FoehnInputComponent` remove `multi: true,`.
@@ -1401,18 +1404,21 @@ You should see in your project root folder `.husky` a new folder `_`.
1401
1404
 
1402
1405
  #### lint-staged
1403
1406
 
1404
- 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:
1405
1408
 
1406
1409
  ```json
1407
- "lint-staged": {
1408
- "*.ts": [
1409
- "eslint --fix",
1410
- "prettier --config ./.prettierrc --write"
1411
- ],
1412
- "*.{js,jsx,json,css,scss,md,html}": [
1413
- "prettier --config ./.prettierrc --write"
1414
- ]
1415
- },
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
+ }
1416
1422
  ```
1417
1423
 
1418
1424
  #### Manually run formatting commands
Binary file