Cannot use pathMatch without redirect or component, etc anymore regression

Which @angular/* package(s) are the source of the bug?

router

Is this a regression?

Yes

Description

After updating to Angular 14, I cannot run my project anymore because of missing element in my routing.

{ path: 'message', component: MessagePageComponent, children: [
   { path: '', pathMatch: 'full', canActivate: [AutoSelectGuard] },
   { path: 'settings', component: MessageSettingsComponent, canActivate: [GroupSelectGuard], children: [
      . . .
    ])
   { path: 'summary', component: MessageSummaryComponent, canActivate: [GroupSelectGuard],

Where on the second line the [AutoSelectGuard], redirects to any sub page, depending on the last time you visited that sub page.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

core.mjs:6412 ERROR Error: Invalid configuration of route 'infotainment//message/'. One of the following must be provided: component, loadComponent, redirectTo, children or loadChildren

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 14.0.1
Node: 16.13.0
Package Manager: npm 8.3.0
OS: win32 x64

Anything else?

After adding “redirectTo:‘settings’” to that second line I got following exception:

core.mjs:6412 ERROR Error: Invalid configuration of route ‘infotainment//message/’: redirectTo and canActivate cannot be used together. Redirects happen before activation so canActivate will never be executed.

So Angular knows I’m using an canActivate guard and it’s mutual exclusive too.

[atscott]

The configuration was never intended to be allowed. Before v14, Lazy loaded configs we’re not validated but now they are. This change is listed in the v14 breaking changes.

The use case you’re describing is a feature gap in the API, which is a duplicate of https://github.com/angular/angular/issues/13373

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}