fix(router): make relativeLinkResolution corrected by default (#25609)
We are changing the default value from 'legacy' to 'corrected' so that new applications are automatically opted-in to the corrected behavior from #22394. BREAKING CHANGE: This commit changes the default value of `relativeLinkResolution` from `'legacy'` to `'default'`. If your application previously used the default by not specifying a value in the `ExtraOptions` and uses relative links when navigating from children of empty path routes, you will need to update your `RouterModule` to specifically specify `'legacy'` for `relativeLinkResolution`. See https://angular.io/api/router/ExtraOptions#relativeLinkResolution for more details. PR Close #25609
This commit is contained in:
parent
bd7d8744fa
commit
837889f0a4
|
@ -443,7 +443,7 @@ export class Router {
|
|||
* Enables a bug fix that corrects relative link resolution in components with empty paths.
|
||||
* @see `RouterModule`
|
||||
*/
|
||||
relativeLinkResolution: 'legacy'|'corrected' = 'legacy';
|
||||
relativeLinkResolution: 'legacy'|'corrected' = 'corrected';
|
||||
|
||||
/**
|
||||
* Creates the router service.
|
||||
|
|
|
@ -425,8 +425,9 @@ export interface ExtraOptions {
|
|||
*
|
||||
* `<a [routerLink]="['../a']">Link to A</a>`
|
||||
*
|
||||
* In other words, you're required to use `../` rather than `./`. This is currently the default
|
||||
* behavior. Setting this option to `corrected` enables the fix.
|
||||
* In other words, you're required to use `../` rather than `./`.
|
||||
*
|
||||
* The default in v11 is `corrected`.
|
||||
*/
|
||||
relativeLinkResolution?: 'legacy'|'corrected';
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue