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
Move all regenerate? checking to Regenerator #3326
Conversation
Cursory glance says 👍 . Will take a closer look tonight. Thank you!! |
} | ||
metadata.write unless full_rebuild? | ||
regenerator.write unless full_rebuild? |
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.
This method is kind of ambiguous.
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.
The naming?
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.
Yeah!
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.
Alright, fixed. It was metadata.write
before, which made sense, but now it's renamed to regenerator.write_metadata
.
LGTM. @envygeeks / @mattr- , wanna take a look? |
👍 |
Thanks!! |
Moves all Post/Page/Document
regenerate?
checking to Regenerator (renamed from Metadata). Also allows non-core objects to be rendered with out an error (fixes #3311)./cc @parkr @envygeeks @crearc