We introduced a localization file clean up script that removes all unused localization keys from the localization files and sorts the remaining keys.
The clean up result is contained in a separate commit that should probably not be applied during a migration and instead a
npm run clean-localizations should be performed on the project sources.
We renamed the testing helper
findAllCustomElements to support project customization.
The returned lists from
findAllDataTestingIDs are no longer sorted to represent the actual template structure.
With Angular version 10.1, the testing utility async was deprecated.
We refactored out code base to use native async/await instead, which was possible in all cases.
The TSLint rule
use-new-async-in-tests takes care of automatically transforming TestBed initialization code in component tests.
Other cases have to be refactored manually.
We removed deprecated exports related to the NgRx testing refactorings introduced in version 0.21.
We switched our main development to the new headless REST application type provided by ICM 220.127.116.11.
If you are upgrading and want to continue using the Responsive Starter Store application types, do not cherry-pick the commits that switch application types.
We refactored the way ICM Http Errors are handled in the PWA.
You can read about it here.
Tests emulating HTTP errors now have to use the helper function
We removed grouping folders of shared components in extensions and sub projects for a better overview.
You can migrate using the script
node schematics/migration/0.22-to-0.23 (for running this script Git version 2.28 or above is recommended since earlier versions resulted in problems).
We deprecated and reworked the way of testing with NgRx.
The old format using
combineReducers is now deprecated and replaced by the new approach.
The old testing mechanism will be removed in version 0.23.
We introduced a way to do shallow testing with feature toggles and used it in the tests.
TSLint rules are set up to automatically fix imports, so run
npm run check after upgrading.
In this version, we decided to start using the ngrx creator introduced in ngrx v8: createAction, createReducer and createEffect.
This means that the old way of writing action classes, reducer switch statements and @effect() decorators is deprecated from 0.21 onwards.
Using these creator functions simplifies code and removes a lot of boiler plate from store files while providing type safety out-of-the-box.
You can automatically migrate your existing code by executing
Doing this will set related ts-lint rules and update each store or notify you of work previously needed.
We upgraded from Angular 8 to version 9 and activated the new rendering engine Ivy with this (following the official upgrade guide).
This was a major upgrade and comes with some changes:
The following changes are available for cherry-picking in one commit:
Angular no longer supports the previously deprecated string syntax for lazy loaded modules. Change it to the dynamic import format.
server.ts was partially rewritten to support SSR dev-server and serverless deployments. Building SSR is now supported by Angular CLI and explicit
webpack builds were removed.
core-js had a major upgrade to version 3, so
polyfill.ts imports have changed.
We temporarily replaced
ngx-utils-cookies-port due to a bug when using Angular 9.1.
angular2-cookie-law was replaced by
ngx-cookie-banner for compatibility reasons. This comes with a styling overhaul.
Further commits contain necessary refactoring:
TestBed.get in tests was deprecated in favor of the new type-safe
The empty generic type for NgRx
Store is now the default and does not have to be supplied. The TSLint rule
ngrx-use-empty-store-type was adapted to apply this refactoring.
We removed lazy loading with
@wishtack/reactive-component-loader and replaced it with the native Angular 9 approach. If you have customized or created extensions, you will have to adapt the following:
Extension export modules are no longer imported and exported in
SharedModule, instead export them in
Instead of pointing to the extension module with
ReactiveComponentLoaderModule in the extension exports module, use the new provider for
LAZY_FEATURE_MODULE pointing to the extension store module, if available. All further lazy loading is done by lazy components and lazy loaded pages. With this, the extension module should no longer import the extension store module.
Lazy components should no longer be part of the repository as they can be auto-generated on
npm install. Use the new decorator
@GenerateLazyComponent() via the
lazy-component schematic to generate lazy components. We currently do not support creating lazy components for components with
@Output() decorated fields.
Previous work-arounds in
<extension>-store.module.ts for adding reducers of selecting the feature state are no longer necessary and can be refactored to standard approaches.
We performed a major upgrade to
prettier which comes with new code formatting for parts of the code.
We replaced VSCode extension
stylelint-plus with the official extension. Update the recommended extensions.
We overhauled the integration of utility libraries for our custom schematics and TSLint rules. These libraries now get built when
We migrated from using ngrx-router to the official and better supported @ngrx/router-store.
This means that throughout the code all usage of the
ofRoute operator and
RouteNavigation actions are no longer available.
As some of these implementations were very specific, we cannot provide a migration script.
In this version change, we decided to no longer recommend the container-component-pattern and therefore changed the folder structure of the project.
We did this because the previously introduced facades provide a more convenient way to interact with the state management and more and more logic was moved out of containers, hence removing all ngrx-related imports there.
You can run the migration by executing
The script will check if all your components can be moved to the new folder structure and will then perform the migration or notify you of work previously needed.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.