Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Nested routes (components) are cached by parent routes (components) #1

Closed
lbwa opened this issue Oct 5, 2018 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@lbwa
Copy link
Owner

lbwa commented Oct 5, 2018

Describe the bug
First-level components are cached by <keep-alive> from first-level <router-view>, including nested components matched nested routes.

To Reproduce
Steps to reproduce the behavior:

  1. Go to /form/step/confirm or /form/step/success
  2. Click on other routes (eg. routes from /form/step/confirm to /dashboard/analysis)
  3. Click button Step form in the aside menu
  4. See error: routes is default matched /form/step/info, but now nested routed is Step.1 matched component.

Expected behavior
Should matched correct nested components.

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser chrome
  • Version 69.0.3497.100

Additional context
<keep-alive> cause this bug (fix) . <keep-alive> cached all first-level matched components, including all nested components matched nested routes.

@lbwa lbwa added the bug Something isn't working label Oct 5, 2018
@lbwa lbwa closed this as completed in 96f1645 Oct 5, 2018
lbwa added a commit that referenced this issue Oct 9, 2018
remove <keep-alive> to prevent unnessary caching for dynamic components
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant