router icon indicating copy to clipboard operation
router copied to clipboard

View caching

Open vlukashov opened this issue 6 years ago • 4 comments

As a developer I want to control when route components are disposed after the user navigates away from them, so that I can set the right balance between resource consumption, performance and UX:

  • keeping stale views in the DOM / memory consumes browser resources
  • repeat navigation to an already rendered view is faster
  • transient UI state is discarded when a view is disposed and sometimes it’s nice to keep it

vlukashov avatar Apr 25 '18 11:04 vlukashov

So important! 👏

abdonrd avatar Jun 12 '18 08:06 abdonrd

Any update on this?

jolleekin avatar Jun 11 '19 19:06 jolleekin

When this feature is implemented, it would be good to make a difference between caching a view instance forever and only preserving the old instance while the user navigates between routes that use the same component, e.g. only changing the value of a parameter.

Legioth avatar Feb 25 '20 10:02 Legioth

Is there any update on this?

omair100 avatar Sep 11 '20 09:09 omair100