Sure there's a way. But the question is, why do you fetch the data from the _component_ each time, perhaps you can keep the data on a service and then define your triggers for refreshing the data.
On Thursday, May 10, 2018 at 5:27:45 PM UTC+2, Reza Razavipour wrote: > > destroyed would mean, recreated, data re-gotten and re-renderered, etc... > > No way to avoid the the destruction and redoing the work that was done > before? > > Regards, > Reza > > On Wed, May 9, 2018 at 11:15 PM, Sander Elias <[email protected] > <javascript:>> wrote: > >> Hi Reza, >> >> I would say router. >> Also, you don't want your components destroyed? (router will do that >> too!). Why not? >> >> Regards >> Sander >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Angular and AngularJS discussion" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/angular/Cf6z3uZd8X8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/angular. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
