What is the difference between $ionicView.enter and cache:false

I really enjoyed this Q & A:

ui.router not reloading controller

Where the Bipin Bhandari nicely summarizes the options we have with ionic caching mechanism

  1. avoid caching by cache: false,
  2. disable caching with $ionicConfigProvider.views.maxCache(0);
  3. or keep caching as is, and let controller be executed only once … while doing some smart stuff during these View LifeCycle and Events

So, with caching in place, controller will be executed just once:

Views are cached to improve performance. When a view is navigated away from, its element is left in the DOM, and its scope is disconnected from the $watch cycle. When navigating to a view that is already cached, its scope is reconnected, and the existing element, which was left in the DOM, becomes active again.

We can hook on these events… to do some “always stuff” with this controller

Leave a Comment