Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

fix(vue-app): Followup for fix for handle prefetch error (#5687) #5690

Merged
merged 1 commit into from
May 10, 2019
Merged

fix(vue-app): Followup for fix for handle prefetch error (#5687) #5690

merged 1 commit into from
May 10, 2019

Conversation

rchl
Copy link

@rchl rchl commented May 10, 2019

Types of changes

  • Bug fix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

After more investigation I've came to conclusion that keeping previous
behavior of marking component as prefetched before we know if it
loaded/failed, is the right thing to do. That's because otherwise, when
processing many nuxt-links within a page, that code will trigger multiple
times, with same component list and trigger loading of them multiple
times (which might be optimized by webpack code anyway but still...).
Resolves: #5687

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly. (PR: #)
  • I have added tests to cover my changes (if not applicable, please state why)
  • All new and existing tests are passing.

After more investigation I've came to conclusion that keeping previous
behavior of marking component as prefetched before we know if it
loaded/failed, is the right thing to do. That's because otherwise, when
processing many nuxt-links within a page, that code will trigger multiple
times, with same component list and trigger loading of them multiple
times (which might be optimized by webpack code anyway but still...).
@rchl
Copy link
Author

rchl commented May 10, 2019

@pi0 @atinux sorry, but I've concluded that I should tweak my fix again

@codecov-io
Copy link

codecov-io commented May 10, 2019

Codecov Report

Merging #5690 into dev will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##              dev    #5690   +/-   ##
=======================================
  Coverage   95.57%   95.57%           
=======================================
  Files          81       81           
  Lines        2645     2645           
  Branches      673      673           
=======================================
  Hits         2528     2528           
  Misses         98       98           
  Partials       19       19

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be18b31...2e4f0ef. Read the comment docs.

@clarkdo clarkdo merged commit 8588ca9 into nuxt:dev May 10, 2019
@rchl rchl deleted the fix/nuxt-link-prefetch-error-followup branch May 10, 2019 09:57
@pi0 pi0 mentioned this pull request May 10, 2019
@atinux
Copy link
Member

atinux commented May 10, 2019

No worries @rchl :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Component loading error during link prefetch is not caught
5 participants