Hi Ronald. I could have worded that more clearly. I meant, make sure there is no state, or so little that's not a problem when it gets lost. If you have only a bit little state, usually the route you are on is enough to retain it. for example. I' on an edit screen. if my route says /module/thingToEdit/idOfthing.. Then something happens, I press f5, and I'm right back where I was, I only lost the edits on that page. Usually, that's a workable tradeoff. If you need more, you need to retain it as I said in local-storage or indexDB
Regards Sander -- 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.
