-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Render new content in "Fast Render Mode" #4339
Comments
I think that was my original idea when I created this, but I have noticed a hole in the logic there myself. A PR for this would be appreciated. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fast Render Mode is a great feature, but I faced with some usability problems with it: when you have a server running and create a new content page, it is added to index (as far as index is always rerendered), but if you try to navigate to this new page, you got 404. I understand the idea behind the Fast Render Mode to render only last visited pages, but there is no way to visit new page, because it's just created.
Even more confusion if you run dev server with
--navigateToChanged
flag, than you instantly redirected to 404 when creating new content page.So my suggestion is: maybe it makes sense to add just created pages to filter of "Recently Visited" and render them too?
If you think it's a good idea, I can prepare pull request for this feature.
The text was updated successfully, but these errors were encountered: