-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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): handle fallback on generated page #7718
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #7718 +/- ##
=======================================
Coverage 68.82% 68.83%
=======================================
Files 90 90
Lines 3820 3821 +1
Branches 1034 1034
=======================================
+ Hits 2629 2630 +1
Misses 968 968
Partials 223 223
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, is it also possible to add a redirect scenario to one of the test fixtures?
Will do :) |
One thing also, because |
Types of changes
Description
This is an advances use case mentioned by @Akryum when you want a static fallback (not SPA) using a
pages/404.vue
and a Netlify redirect. Hitting an unknown page will fetch the wrong payload, this is why I useNUXT.routePath
to fetch the generated page to fetch the payload.@pi0 I am wondering if we should no directly remove
_app.context.route.path
directly infetchPayload(NUXT.routePath || _app.context.route.path)
Checklist: