-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
feat: bring up config.updated_option #4278
Conversation
Without |
Comment out that line and mention this PR. Since the default behavior is still retained, no breaking change then? |
@curbengh Done. The PR is now ready for reivew. |
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.
Tested working.
- post.updated will be null if not set in front-matter - hexojs/hexo#4278
I re-label this as breaking change due to https://github.com/hexojs/hexo/pull/4278/files#diff-a17a4a3f711955a771f0f61a61525fd9L30, |
What does it do?
Continuation of #3235, specifically #3235 (comment). #3887 (comment)
Quote from #3887
This PR introduced a new option
updated_option
which accept:mtime
: This is the default behavior of hexo, use file'smtime
asdata.updated
when not set in front-matter.date
: Usedata.date
asdata.updated
when not set in front-matter.empty
: Completely removedata.updated
when not set in front-matter. This shouldn't be used by common users as it will break many themes (like NexT) and plugins (like hexo-generator-feed)The
use_date_for_updated
introduced in hexo v4 is still retained, and still has higher priority thanupdated_option
(That's mean whenuse_date_for_updated
is set to true,updated_option
will be ignored).Breaking changes
See #3887 for more details.
How to test
Screenshots
Pull request tasks