Skip to content

refactor(router): Implement page navigation with RouteReuseStrategy (#949) #977

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 7, 2017

Conversation

vakrilov
Copy link
Contributor

@vakrilov vakrilov commented Sep 4, 2017

Use RouteReuseStrategy implementation to do page navigation with <page-router-outlet>

@ghost ghost assigned vakrilov Sep 4, 2017
@ghost ghost added the in progress label Sep 4, 2017
@vakrilov vakrilov force-pushed the route-reuse-strategy branch 2 times, most recently from ab952e0 to 497f56d Compare September 4, 2017 13:01
@vakrilov vakrilov requested a review from sis0k0 September 5, 2017 12:37
@sis0k0 sis0k0 force-pushed the route-reuse-strategy branch from d8302c4 to 85e4e35 Compare September 7, 2017 13:13
@ghost ghost assigned sis0k0 Sep 7, 2017
@vakrilov vakrilov merged commit 78e6625 into master Sep 7, 2017
@ghost ghost removed the in progress label Sep 7, 2017
@vakrilov vakrilov deleted the route-reuse-strategy branch September 7, 2017 17:19
@jogboms
Copy link

jogboms commented Sep 10, 2017

Thanks @vakrilov. This fixed the clearHistory issue. 👍

@jogboms
Copy link

jogboms commented Sep 10, 2017

JS: ERROR Error: Uncaught (in promise): Error: Currently not in page back navigation - component should be detached instead of deactivated.
JS: Error: Currently not in page back navigation - component should be detached instead of deactivated.
JS:     at PageRouterOutlet.deactivate (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/nativescript-angular/router/page-router-outlet.js:134:19) [angular]
JS:     at ActivateRoutes.deactivateRouteAndOutlet (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4544:32) [angular]
JS:     at ActivateRoutes.deactivateRouteAndItsChildren (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4514:18) [angular]
JS:     at ActivateRoutes.deactivateRoutes (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4500:22) [angular]
JS:     at file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4466:19 [angular]
JS:     at Array.forEach (native) [angular]
JS:     at ActivateRoutes.deactivateChildRoutes (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4464:29) [angular]
JS:     at ActivateRoutes.activate (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4450:14) [angular]
JS:     at file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/@angular/router/bundles/router.umd.js:4064:22 [angular]
JS:     at SafeSubscriber._next (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/rxjs/Observable.js:224:21) [angular]
JS:     at SafeSubscriber.__tryOrSetError (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/rxjs/Subscriber.js:247:16) [angular]
JS:     at SafeSubscriber.next (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/rxjs/Subscriber.js:187:27) [angular]
JS:     at Subscriber._next (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/rxjs/Subscriber.js:125:26) [angular]
JS:     at Subscriber.next (file:///data/data/com.rfnl.fixershubclient/files/app/tns_modules/rxjs/Subscriber.js:89:18) [angular]

Any particular reason why i would be getting this for a forward navigation?

    "@angular/router": "^4.2.6",
    "nativescript-angular": "^4.3.0-2017-9-7-3",
    "tns-core-modules": "^3.2.0",

@vakrilov
Copy link
Contributor Author

There is a problem with the new routing-strategy when using lazy-modules. We will be looking into this in a next few days. Hopefully there will be another patch soon.

@jogboms
Copy link

jogboms commented Sep 11, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants