-
-
Notifications
You must be signed in to change notification settings - Fork 1k
docs: add app.config route to pre-render #8131
Conversation
Β Open in CodeSandbox Web Editor | VS Code | VS Code Insiders |
β Deploy Preview for nuxt3-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
https://github.com/nuxt/content/blob/main/src/runtime/pages/document-driven.vue Docus has no "default" components for DocumentDrivenNotFound and DocumentDrivenEmpty components, but I guess this is the way to go for this kind of issues. I remember that there was an "issue" (maybe this is expected behavior) with catch-all pages that was overriding the support for error pages in Maybe we could work around this by throwing an error in DocumentDriven page when the query fails, and then handling the 404 via Nuxt pages folder? I also know that as |
If we have a design for a custom error page, we can provide it in The 404 error is only being thrown on server side in docus, which means we're not redirected to it on a client-side 404 (in this case), and the console errors are coming from missing nav data (owing to not having a defined GITHUB_TOKEN) on client side. We should likely gracefully handle them as well. |
It the comment blocking the current PR? |
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.
No, this is good to go π
Just a little info, this can only be reproduced on built version, when using I just locally tried creating both:
It doesn't had any effect in built versions, I suspect this is upstream issue as mentioned, |
π Linked issue
β Type of change
π Description
Add missing url not detected by crawler π€
π Checklist