Andrew Scott
Andrew Scott
Please provide a runnable reproduction. There’s not enough information here to determine the issue but on the surface, the behavior seems likely correct as you’re using `snapshot`, which is exactly...
The reproduction doesn’t have `provideRouter` with any routes. Is that intended?
Closing as this issue has become more of a support request and requires a reproduction in order to debug. (Reproductions can be GitHub repositories). Please open a new issue with...
This PR was merged into the repository by commit abdf453b85477ace0d6a3ddebeb3663edc1629bc.
> In my prototyping, I have been trying to achieve signal based components and directives with no Angular lifecycle methods (ngOnChanges, ngOnInit, etc.). > I am not seeing a way...
This PR was merged into the repository by commit 2bb12ac02f8a0f766f6a38d4f3704eaebe58d402.
This is not a compilation error so there will not be an error displayed in the language service. Moving to the main angular/angular repo, as this could be addressed by...
`child-routing.module.ts` uses `RouterModule.forRoot` but this should be `forChild`. Closing as an application issue.
I've made a much smaller reproduction here: https://stackblitz.com/edit/stackblitz-starters-ew6f7z (again, it has to be downloaded and run locally)
These changes seem reasonable, though there may be some amount of difficulty determining if the router is "on the same page" or not, especially when considering multiple outlets. Let's start...