diff --git a/src/app/recommendations.ts b/src/app/recommendations.ts index c4539c5..b316fcd 100644 --- a/src/app/recommendations.ts +++ b/src/app/recommendations.ts @@ -173,7 +173,7 @@ export const RECOMMENDATIONS: Step[] = [ { possibleIn: 1300, necessaryAsOf: 1300, level: 2, step: 'v13 service worker available', action: 'The `available` observable of `SwUpdate` is now deprecated. To get the same information use `versionUpdates` and filter only the `VersionReadyEvent` events.' }, { possibleIn: 1300, necessaryAsOf: 1300, level: 2, step: 'v13 renderModuleFactory', action: 'The `renderModuleFactory` from `@angular/platform-server` is no longer necessary with Ivy. Use `renderModule` instead.' }, { possibleIn: 1300, necessaryAsOf: 1300, level: 3, step: 'v13 forms status', action: 'We narrowed the type of `AbstractControl.status` to `FormControlStatus` and `AbstractControl.status` to `Observable`. `FormControlStatus` is the union of all possible status strings for form controls.' }, - { possibleIn: 1300, necessaryAsOf: 1300, level: 3, step: 'v13 router serializer', action: 'To align with the URI spec, now the URL serializer respects question marks in the query parameters. For example `/path?q=hello?&q2=2` will now be parsed to `{ q: `hello?`, q2: 2 }`' }, + { possibleIn: 1300, necessaryAsOf: 1300, level: 3, step: 'v13 router serializer', action: 'To align with the URI spec, now the URL serializer respects question marks in the query parameters. For example `/path?q=hello?&q2=2` will now be parsed to `{ q: \'hello?\', q2: 2 }`' }, { possibleIn: 1300, necessaryAsOf: 1300, level: 3, step: 'v13 host binding', action: '`href` is now an attribute binding. This means that `DebugElement.properties[\'href\']` now returns the `href` value returned by the native element, rather than the internal value of the `href` property of the `routerLink`.' }, { possibleIn: 1300, necessaryAsOf: 1300, level: 3, step: 'v13 spy location', action: '`SpyLocation` no longer emits the `popstate` event when `location.go` is called. In addition, `simulateHashChange` now triggers both `haschange` and `popstate`. Tests that rely on `location.go` most likely need to now use `simulateHashChange` to capture `popstate`.' }, { possibleIn: 1300, necessaryAsOf: 1300, level: 3, ngUpgrade: true, step: 'v13 router URL replacement', action: 'The router will no longer replace the browser URL when a new navigation cancels an ongoing navigation. Hybrid applications which rely on the `navigationId` being present on initial navigations that were handled by the Angular router should subscribe to `NavigationCancel` events and perform the `location.replaceState` to add `navigationId` to the `Router` state. In addition, tests which assert `urlChanges` on the `SpyLocation` may need to be adjusted to account for the `replaceState` which is no longer triggered.' },