My main thinking is that I want to minimize my dependency on Ionic internals. If Ionic changes under the hood how lifecycle is managed, maybe tomorrow the Angular events won’t fire when I’m expecting (or maybe at all in some cases). I figure the Ionic events are documented, so they will maintain that compatibility. I also find
ionViewWillEnter simultaneously widely useful (in fact, it is what I would use for this topic, as presumably one would want the form to get reset every time the page is activated, even if it is from a cache) and having no direct Angular equivalent.
I would agree with you and even say more strongly that that’s your only option. Embedded components don’t get
NavController lifecycle calls. My apologies if that’s the case for this thread: I didn’t examine the plunkr thing in the OP.