You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
It appears that latest changes to this function affect this functionality.
export function findTopActivatedRouteNodeForOutlet(activatedRoute: ActivatedRouteSnapshot): ActivatedRouteSnapshot {
// TODO: test this and figure it out if it's really no longer needed
return activatedRoute;
// let outletActivatedRoute = activatedRoute;
// while (outletActivatedRoute.parent && outletActivatedRoute.parent.routeConfig && !outletActivatedRoute.parent.routeConfig.component) {
// outletActivatedRoute = outletActivatedRoute.parent;
// }
// return outletActivatedRoute;
}
When reverting this change back (uncomment) it is working, but reloading the whole frame.
The text was updated successfully, but these errors were encountered:
Environment
Provide version numbers for the following components (information can be retrieved by running
tns info
in your project folder or by inspecting thepackage.json
of the project):Describe the bug
I get an error: "ns-router: No outlet found relative to activated route" when navigating back in nested route (one with a named outlet) .
I debug it until this function: findTopActivatedRouteNodeForOutlet in
https://github.com/NativeScript/angular/blob/main/packages/angular/src/lib/legacy/router/page-router-outlet-utils.ts
It appears that latest changes to this function affect this functionality.
When reverting this change back (uncomment) it is working, but reloading the whole frame.
The text was updated successfully, but these errors were encountered: