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

Render new content in "Fast Render Mode" #4339

Closed
yanzay opened this issue Jan 27, 2018 · 2 comments
Closed

Render new content in "Fast Render Mode" #4339

yanzay opened this issue Jan 27, 2018 · 2 comments

Comments

@yanzay
Copy link
Contributor

yanzay commented Jan 27, 2018

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.

@yanzay yanzay changed the title Rendering new content in "Fast Render Mode" Proposal: Rendering new content in "Fast Render Mode" Jan 27, 2018
@bep
Copy link
Member

bep commented Jan 27, 2018

So my suggestion is: maybe it makes sense to add just created pages to filter of "Recently Visited" and render them too?

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.

@bep bep changed the title Proposal: Rendering new content in "Fast Render Mode" Render new content in "Fast Render Mode" Jan 27, 2018
@bep bep added this to the v0.36 milestone Jan 27, 2018
yanzay added a commit to yanzay/hugo that referenced this issue Jan 28, 2018
@bep bep modified the milestones: v0.36, v0.35 Jan 29, 2018
@bep bep closed this as completed in 94e736c Jan 30, 2018
@github-actions
Copy link

github-actions bot commented Mar 8, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants