Add canDeactivateChild guard

[marcelgood]

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

What is the motivation / use case for changing the behavior?
There is already a canActivateChild guard. Having the symmetric guard is equally important. Not sure why this wasn't added at the same time. We have many scenarios where we need to protect child routes from navigating away if they have pending unsaved changes. That's currently only possible by putting a canDeactivate guard on each child route.

• Angular version: Latest
• Browser: all
• Language: all

[nlgi]

+1, as canActivateChild, we have to deactivate child route.

Is that possible without a new "canDeactivateChild guard"?

Many thanks,

[popinguy]

Are there any news for this issue? Or are there any other solutions as @nlgi asked?
Thanks

[vitorrd]

Anything on this? I really wouldn't like to edit Ng2 from the inside, but that's what I've done so far.

@vitorrd have you make a turn around about this issue by editing Ng2 from the inside? I tried to follow the steps provided by tdsmithATabc from #11664 (it's at the end of the page) but I can't make it work yet.

[vitorrd]

@fenderjair It seems the fix provided is fairly useful in some cases, just not in mine. What I want is to avoid any navigation while a custom popup is open, so I need to cover a big amount of routes.

[patrickpereira]

+1 Needed for lazyloaded routes

[hydralix]

+1

[elvisbegovic]

any news here ? this feature request is missing to fix my usecase.

actually I have to specify canDeactivate:[CanDeactivateEntityGuard] in all child. With feature like canDeactivateChild I coul'd specify it only once in routes[] array used in forRoot()

canDeactivateChild need call my guard each time when child route or sub-child or sub-sub-child route change.

Actually, is there better way to avoid write it in every routes child? I mean handle all route deactivation and call my guard?
merci
cc @vicb

[erc-s-arai]

are there any news or solution here?
I would need canDeactivateChild at least in next year.

Please tell me about when will that be fixed?

[jtkDvlp]

are there any news, solution or workarounds here?

[elvisbegovic]

+2

[spoddutu]

+1. As of now any news on this issue?

And BTW below is path i took to implement this as of now. Please suggest in case of any better Path

Listening to valueChanges event of the NgForm and emitting an event from child component and subscribing it in parent to return proper value when Deactivate guard is fired.