@dsivd/prestations-ng 19.0.0-beta.6 → 19.0.0-beta.8

package/CHANGELOG.md

@@ -22,6 +22,23 @@
 - [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

@@ -19,13 +19,13 @@ in both the Dev Tool and the library reload the page.
 ## Testing the library in integration
 
 Since version `8`, we can't use native symlink to integrate `prestations-ng` to
-a prestation such as Skeleton. We can however use `yarn link` to achieve the same
+a prestation such as Skeleton. We can however use `npm link` to achieve the same
 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).
@@ -33,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)**
 
@@ -64,12 +64,12 @@ 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 && yarn link` (it's critical to link the content of `dist/prestations-ng`, not the root)
-    - `npm run build:lib:dev` (at root level)
+    - `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)
 
 - **In project**:
     - `cd front`
-    - `yarn link @dsivd/prestations-ng` (`yarn 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/UPGRADING_V19.md

@@ -153,6 +153,13 @@ Run your application with this dependency :
 
 Look for logs that indicate property you should migrate (watch for WARN logs of class PropertiesMigrationListener), update them and remove the dependency
 
+### BO using jpa repositories
+
+As we also have jdbc in the classpath, to avoid having dozens of log like "Spring Data JDBC - Could not safely 
+identify store assignment for repository candidate interface", add the property in your application.properties :
+
+spring.data.jdbc.repositories.enabled=false
+
 ### Debugging tips
 
 Spring boot 4 doesn't support calling a controller with a trailing slash, fix the url called (/api/ping != /api/ping**/**)
@@ -330,7 +337,7 @@ ng update ngx-matomo-client@9
 
 ### Quick fix
 
-In all custom components extending `FoehnInputComponent`, in `providers` providing `FoehnInputComponent` remove `multi: true,`
+- In all custom components extending `FoehnInputComponent`, in `providers` providing `FoehnInputComponent` remove `multi: true,`.
 
 ```diff
 {
@@ -340,9 +347,11 @@ In all custom components extending `FoehnInputComponent`, in `providers` providi
 }
 ```
 
-In your `.eslintrc.json`, remove `"/src/main.ts",` from `ignorePatterns`
+- In your `.eslintrc.json`, remove `"/src/main.ts",` from `ignorePatterns`.
 
-In `main.ts`, replace `platformBrowserDynamic` by `platformBrowser`
+- In `main.ts`, replace `platformBrowserDynamic` by `platformBrowser`.
+
+- When using `<foehn-list-summary` component, replace `list` by `model`.
 
 ### Now fix your project before continuing
 
@@ -426,6 +435,8 @@ ng generate @angular/core:self-closing-tag
 
 **WARNING: The following command will work only when your application compiles without errors. If you have errors, fix them before continuing.**
 
+**TIP: Check [Migrating from NgModules](COMPONENTS.md#migrating_from_ngmodules) for more information before running following commands.**
+
 ```bash
 npm run build
 ```