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

last_updated vs last_modified_at for posts #2598

Open
2 tasks done
sim642 opened this issue Jul 24, 2024 · 1 comment
Open
2 tasks done

last_updated vs last_modified_at for posts #2598

sim642 opened this issue Jul 24, 2024 · 1 comment

Comments

@sim642
Copy link
Contributor

sim642 commented Jul 24, 2024

Have you checked that your feature request isn't already filed?

  • I read through FAQ and searched through the past issues, none of which addressed my feature request.
  • Yes, I have checked that this feature request isn't already filed.

Description & Motivation

#2341 added the last_updated field to posts. However, jekyll-sitemap, which is included here, uses last_modified_at instead. This requires duplicating the date in two fields.

Pitch

Transition to last_modified_at field instead:

  1. Use last_modified_at to output what last_updated is used for right now.
  2. Direct new users to use last_modified_at for that purpose.

For backwards-compatibility last_updated should be used as fallback.

Alternatives

No response

Additional context

No response

@george-gca
Copy link
Collaborator

Could you send a PR for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants