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

Smarter rebuild on content change #59

Closed
Keats opened this issue May 8, 2017 · 1 comment
Closed

Smarter rebuild on content change #59

Keats opened this issue May 8, 2017 · 1 comment

Comments

@Keats
Copy link
Collaborator

Keats commented May 8, 2017

I'm currently leaving TODOs all over the place so the rebuild_after_content_change will take as little time as possible.
Do it once the new way of handling index is in

@Keats
Copy link
Collaborator Author

Keats commented May 11, 2017

#62 is a first step to make things faster when editing the content of a page.

There are a few other situations:

  • editing front matter of a page: need to check what changed to know what to re-render but even then since people can put whatever in extra you're never sure what should be changed. Might be safer to just re-render the whole section if there is one, tags/categories if they changed and index.

  • deleting a page: should re-render the section if there is one, index page and tags/categories if there were some

  • deleting a section: should re-sort/set prev&next to pages int the section and re-render index

Need to see what happens in terms of event when doing bulk actions, like renaming a folder for example.

@Keats Keats closed this as completed in 09d5e74 May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant