feat: angular 21generator#348
Conversation
|
will the renaming of the package also be included in this ticket? |
Will push a new PR once this is merged as it does have a lot of file changes |
Co-authored-by: Copilot <copilot@github.com>
| @@ -1,5 +1,13 @@ | |||
| import { setupZoneTestEnv } from 'jest-preset-angular/setup-env/zone' | |||
|
|
|||
| // JSDOM does not implement `innerText` which is used by Angular's testing utilities. This causes tests to fail with: | |||
There was a problem hiding this comment.
"This causes tests to fail with: " -> is this unfinished?
| const oneCXLibVersion = '^7.7.2'; | ||
| const angularVersion = '^20.3.9'; | ||
| const oneCXLibVersion = '^8.2.2'; | ||
| const angularVersion = '21.2.9'; |
There was a problem hiding this comment.
| const angularVersion = '21.2.9'; | |
| const angularVersion = '^21.2.9'; |
There was a problem hiding this comment.
With new module federation:
- requiredVersion = package.json version
- providedVersion = package-lock.json version
Because of this, we should use ^21.0.0 for every generated app.
| '@ngrx/component': '21.1.0', | ||
| '@ngrx/effects': '21.1.0', | ||
| '@ngrx/router-store': '21.1.0', | ||
| '@ngrx/store': '21.1.0', | ||
| '@ngrx/store-devtools': '21.1.0', |
There was a problem hiding this comment.
| '@ngrx/component': '21.1.0', | |
| '@ngrx/effects': '21.1.0', | |
| '@ngrx/router-store': '21.1.0', | |
| '@ngrx/store': '21.1.0', | |
| '@ngrx/store-devtools': '21.1.0', | |
| '@ngrx/component': '^21.1.0', | |
| '@ngrx/effects': '^21.1.0', | |
| '@ngrx/router-store': '^21.1.0', | |
| '@ngrx/store': '^21.1.0', | |
| '@ngrx/store-devtools': '^21.1.0', |
| '@ngrx/store-devtools': '21.1.0', | ||
| '@webcomponents/webcomponentsjs': '^2.8.0', | ||
| 'zone.js': '~0.15.0', | ||
| 'zone.js': '0.16.1', |
There was a problem hiding this comment.
| 'zone.js': '0.16.1', | |
| 'zone.js': '~0.16.1', |
| '@angular/platform-browser-dynamic': angularVersion, | ||
| '@angular/router': angularVersion, | ||
| primeflex: '^3.3.1', | ||
| primeflex: '^4.0.0', |
There was a problem hiding this comment.
Do we need to update primeflex to avoid dependency issues? If not I would not do that since we should move to tailwind anyways.
| 'angular-eslint': '21.3.1', | ||
| '@angular-eslint/builder': '21.3.1', | ||
| '@angular-eslint/eslint-plugin': '21.3.1', | ||
| '@angular-eslint/eslint-plugin-template': '21.3.1', | ||
| '@angular-eslint/schematics': '21.3.1', | ||
| '@angular-eslint/template-parser': '21.3.1', |
There was a problem hiding this comment.
| 'angular-eslint': '21.3.1', | |
| '@angular-eslint/builder': '21.3.1', | |
| '@angular-eslint/eslint-plugin': '21.3.1', | |
| '@angular-eslint/eslint-plugin-template': '21.3.1', | |
| '@angular-eslint/schematics': '21.3.1', | |
| '@angular-eslint/template-parser': '21.3.1', | |
| 'angular-eslint': '^21.3.1', | |
| '@angular-eslint/builder': '^21.3.1', | |
| '@angular-eslint/eslint-plugin': '^21.3.1', | |
| '@angular-eslint/eslint-plugin-template': '^21.3.1', | |
| '@angular-eslint/schematics': '^21.3.1', | |
| '@angular-eslint/template-parser': '^21.3.1', |
| jest: '^30.0.0', | ||
| 'jest-environment-jsdom': '^30.0.0', | ||
| 'jest-preset-angular': '^16.0.0', | ||
| 'jest-preset-angular': '16.1.4', |
There was a problem hiding this comment.
| 'jest-preset-angular': '16.1.4', | |
| 'jest-preset-angular': '^16.1.4', |
| '@ngrx/effects': '21.1.0', | ||
| '@ngrx/router-store': '21.1.0', | ||
| '@ngrx/store': '21.1.0', | ||
| '@ngrx/component': '21.1.0', | ||
| '@ngrx/store-devtools': '21.1.0', |
There was a problem hiding this comment.
| '@ngrx/effects': '21.1.0', | |
| '@ngrx/router-store': '21.1.0', | |
| '@ngrx/store': '21.1.0', | |
| '@ngrx/component': '21.1.0', | |
| '@ngrx/store-devtools': '21.1.0', | |
| '@ngrx/effects': '^21.1.0', | |
| '@ngrx/router-store': '^21.1.0', | |
| '@ngrx/store': '^21.1.0', | |
| '@ngrx/component': '^21.1.0', | |
| '@ngrx/store-devtools': '^21.1.0', |
| readonly locale = inject(LOCALE_ID); | ||
|
|
||
| calendars = viewChildren(DatePicker) | ||
| // TODO: use signal after updating libs and pass appropriate value accordingly in buildSearchCriteria. |
There was a problem hiding this comment.
we should use the new utility here
|
Added to draft for now
|
No description provided.