Andrew Scott
Andrew Scott
Just looking at what’s written, since there’s no runnable reproduction, the two are not equivalent in their nesting. The example without loadChildren should be: ``` export const routes: Routes =...
`vi.useFakeTimers` can be used and you should stick to the async variants `vi.tickAsync`/`vi.runAllTimersAsync`/etc to allow the microtask queue to drain between each task.
Confirmed in v9 as well: https://stackblitz.com/edit/angular-7fpprl-ft1ezk?file=main.ts, https://angular-7fpprl-ft1ezk.stackblitz.io/#qwe
> Is it possible for the Angular team to provide a status for this issue There is no update on this issue, nor is any work planned for it at...
[TGP](https://fusion2.corp.google.com/presubmit/720242782/OCL:720242782:BASE:720180594:1738024322903:600ea433/targets) shows 21 failures, many of which are due to 0-1 query. There are a handful of others that will need some more digging. The results here sound quite similar...
Closing, per https://github.com/angular/angular/pull/58580#issuecomment-2622389064
You _really_ cannot reuse the `ActivatedRoute` instance that matched to the route with `{path: 'Bar', data: {path: '/Foo/Bar - root'}, children: [...]}` for the route `{path: '', pathMatch: "full", component:...
I think @alxhub should probably review this
Yea, that's definitely an issue. There's currently no way to control whether scroll happens on an individual navigation but that should change soon (https://github.com/angular/angular/pull/64417). Once that's in place, perhaps the...
Please provide a reproduction. The given steps alone would not result in the error.