@dsivd/prestations-ng 19.0.0-beta.1 → 19.0.0-beta.11

package/.browserslistrc

@@ -1,11 +1,24 @@
-# Se mettre à la racine du projet
-# Mettre à jour avec "npx browserslist --update-db"
-# Valider le contenu de ce fichier avec `npx browserslist --coverage=CH "> 2% in CH, last 2 versions, not dead, Firefox ESR, not IE_Mob <= 11, not IE <= 11"`
-# Le pourcentage accepté doit être supérieur à 80%
-# Regénérer le fichier "supported-browsers.ts" avec "npm run buildScript:generateBrowsersList"
+# Se mettre a la racine du projet
+# Mettre a jour avec "npx browserslist --update-db"
+# Ce bloc par defaut est consomme par Angular CLI.
+# Regenerer le fichier "supported-browser.ts" avec "npm run buildScript:generateBrowsersList"
 #######################################################################################################################################################################################
-# Liste des navigateurs supportés
+# Liste des navigateurs supportes par Angular CLI (evite les warnings "Unsupported browsers")
 #######################################################################################################################################################################################
+last 2 Chrome major versions
+last 2 Edge major versions
+last 2 Firefox major versions
+Firefox ESR
+last 2 and_chr major versions
+not dead
+# Maintenance: passer a 19.x (puis 20.x, ...) quand la matrice de support Angular l'autorise.
+ios_saf 18.0-18.99
+safari 18.0-18.99
+
+[supportedBrowsersRegex]
+# Valider ce bloc avec:
+# npx browserslist --config=src/.browserslistrc --env=supportedBrowsersRegex --coverage=CH
+# Le pourcentage accepte doit etre environ 80%
 > 2% in CH
 last 2 versions
 not dead

package/ANGULAR_SIGNALS.md

@@ -771,13 +771,7 @@ const items = [...this.daysButtons()];
 const items = [...(this.daysButtons() ?? [])];
 ```
 
-### 6. Expecting `[binding]` to work with `model()`
-
-`model()` only accepts `[(two-way)]` or the split form
-`[value]="x" (valueChange)="x = $event"`.
-A plain `[binding]` will produce a compiler error.
-
-### 7. Over-tracking inside `effect()` — forgetting `untracked()`
+### 6. Over-tracking inside `effect()` — forgetting `untracked()`
 
 An `effect()` tracks **every** signal it reads, not just the ones you
 intended as triggers. Reading a signal "just to get its current value"
@@ -805,7 +799,7 @@ effect(() => {
 });
 ```
 
-### 8. Using `untracked()` instead of an equality check
+### 7. Using `untracked()` instead of an equality check
 
 `untracked()` controls what _triggers_ an effect — it does not make a write
 inside the effect "safe" by itself. If the effect's only tracked dependencies
@@ -834,7 +828,7 @@ effect(() => {
 });
 ```
 
-### 9. Mutating a `model()`'s nested object instead of reassigning
+### 8. Mutating a `model()`'s nested object instead of reassigning
 
 This is the signals-era version of "mutating `@Input()` used to work."
 Pre-signals, Zone.js-driven change detection re-read template expressions

package/CHANGELOG.md

@@ -6,6 +6,39 @@
 
 ---
 
+## [19.0.0] - should be aligned with prestations-be 19.0.x
+
+### Added
+
+- [UPGRADING_V19](UPGRADING_V19.md)
+    - Added migration guide
+
+- [string.helper.ts](projects/prestations-ng/src/helpers/string.helper.ts)
+    - Added a helper for string manipulation
+
+- [dictionary-type.ts](projects/prestations-ng/src/sdk-dictionary/dictionary-type.ts)
+    - Added dictionary `PlaceholderType` type, `DictionaryType` type and `Language` interface
+
+- [HasCustomErrors](projects/prestations-ng/src/has-custom-errors.ts)
+    - Added `HasCustomErrors` interface representing a component that has custom error messages
+
+- [foehn-header.component.html](projects/prestations-ng/src/foehn-header/foehn-header.component.html)
+    - Added a few more ids
+
+### Updated
+
+- [foehn-footer.component.ts](projects/prestations-ng/src/foehn-footer/foehn-footer.component.ts)
+    - Updated default guide link URL
+
+- [foehn-input.component.ts](projects/prestations-ng/src/foehn-input/foehn-input.component.ts)
+    - `[name]` attribut is required
+    - `[model]` attribut is required
+
+### Deleted
+
+- [foehn-list-summary.component.ts](projects/prestations-ng/src/foehn-menu-prestation/foehn-list-summary/foehn-list-summary.component.ts)
+    - `[list]` attribut has been removed. Use `[model]` instead.
+
 ## [18.3.12]
 
 ### Updated

package/CONTRIBUTING.md

@@ -2,19 +2,10 @@
 
 ## Prerequisite
 
-- Node 20.11+
+- Node 22.18+
 - npm 10.2+
 - Chrome or Chromium
 - G++
-- The variable `CHROMIUM_BIN` set in your environment
-
-If you're using bashrc.dev.pee, the variable `CHROMIUM_BIN` is already set to `~/slave-apps/chromium-headless-64/chrome`
-
-If not, you can set the variable in your `.bashrc` or `.zshrc`:
-
-```bash
-export CHROMIUM_BIN=/usr/bin/google-chrome-stable
-```
 
 ## Developing using the Dev Tool
 
@@ -34,7 +25,7 @@ result.
 ### In **prestations-ng**
 
 - if it is the first time, execute `npm install` then `npm run build:lib` (at root level)
-- `cd dist/prestations-ng && yarn link` (it's critical to link the content of `dist/prestations-ng`, not the root)
+- `cd dist/prestations-ng && npm link` (it's critical to link the content of `dist/prestations-ng`, not the root)
 - `cd ../.. && npm run build:lib:dev` (at root level)
 
 `build:lib:dev` will use a feature of the Angular CLI: `--watch`. For more information on `--watch`, refer to the [official documentation](https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/create-library.md#why-do-i-need-to-build-the-library-everytime-i-make-changes).
@@ -42,12 +33,12 @@ result.
 ### In the prestation
 
 - `cd front`
-- `yarn link @dsivd/prestations-ng`
+- `npm link @dsivd/prestations-ng`
 - `npm start` (only when `npm run build:lib:dev` in `prestations-ng` has started)
 
 Now if you change something in `prestations-ng`, the CLI of the prestation will hot swap the missing pieces and reload the page.
 
-Finally, when you're done, run `yarn unlink @dsivd/prestations-ng` to unlink the local version. You will need to run `npm install --force` to re-install the package that was linked.
+Finally, when you're done, run `npm install` to unlink the local version.
 
 **NB: When the project uses a version 12+ or 13+ of the library, you need to use `yarn start:symlink` and checkout the library tag matching v12+ or v13+. More information on [UPGRADING_V12](UPGRADING_V12.md)**
 
@@ -74,11 +65,11 @@ run `npm run test:schematics` (at root level).
 - **In prestations-ng**:
     - if it is the first time, execute `npm install` then `npm run build:lib` (at root level)
     - `cd dist/prestations-ng && npm link` (it's critical to link the content of `dist/prestations-ng`, not the root)
-    - `npm run build:lib:dev` (at root level)
+    - `cd ../.. && npm run build:lib:dev` (at root level)
 
 - **In project**:
     - `cd front`
-    - `npm link @dsivd/prestations-ng` (`npm unlink @dsivd/prestations-ng` to remove link)
+    - `npm link @dsivd/prestations-ng` (`npm install` to remove link)
     - `ng g @dsivd/prestations-ng:[YOUR_SCHEMATIC]` (i.e. `ng g @dsivd/prestations-ng:ng-add` or `ng g @dsivd/prestations-ng:update-karma-config` or `ng g @dsivd/prestations-ng:replace-browsers-list`)
 
 In your project, you can test any schematic added into [collection.json](projects/prestations-ng/schematics/collection.json).

package/README.md

@@ -8,6 +8,7 @@ The generated documentation of our entire library is available online at [https:
 
 The documentation is available online at [https://dsi-vd.github.io/prestations-ng/](https://dsi-vd.github.io/prestations-ng/)
 
+- If you're using **Angular 21**, use `@dsivd/prestations-ng` at version `^19`.
 - If you're using **Angular 19**, use `@dsivd/prestations-ng` at version `^18`.
 - If you're using **Angular 17**, use `@dsivd/prestations-ng` at version `^17`.
 - If you're using **Angular 15**, use `@dsivd/prestations-ng` at version `^16`.