Skip to content

Conversation

@suresh-gangumalla
Copy link
Collaborator

  1. On navigating using $route.to method, always create new instance of component eventhough its already cached by keepAlive
  2. Not removing keepAlive pages from cache on back navigation
  3. Destroying non keep alive pages on route change

1. On navigating using $route.to method, always create new instance of
   component eventhough its already cached by keepAlive
2. Not removing keepAlive pages from cache on back navigation
3. Destroying non keep alive pages on route change

Signed-off-by: Suresh Kumar Gangumalla <[email protected]>
@github-actions
Copy link

Test Results Summary: (Ran at: Wed Mar 19 10:38:48 UTC 2025)
passed: 491 failed: 0 of 491 tests (767ms)

Added feature to store multiple instances of same route hash
on navigating and implemented removing & destroying specific entry
as per route history

Signed-off-by: Suresh Kumar Gangumalla <[email protected]>
@github-actions
Copy link

Test Results Summary: (Ran at: Tue Mar 25 09:22:06 UTC 2025)
passed: 491 failed: 0 of 491 tests (747ms)

@github-actions
Copy link

github-actions bot commented Apr 8, 2025

Test Results Summary: (Ran at: Tue Apr 8 08:42:48 UTC 2025)
passed: 491 failed: 0 of 491 tests (774ms)

@michielvandergeest
Copy link
Collaborator

@suresh-gangumalla - I think this PR has been addressed differently in the v1.39.0 release? Correct?

@suresh-gangumalla
Copy link
Collaborator Author

Yes @michielvandergeest this was handled in latest release so we are good to close this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants