-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Add support for git creation date #2579
Conversation
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.
Sorry for nit-picking but spent too much time with doc writing and couldn't resist. HTH
On the contrary, it shows you care. Much appreciated! Addressed the feedback in 33212c5 |
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.
Thanks for taking the time to add support for this nice little plugin 🚀 Going down the path of adding support for more and more git-related information, I'd suggest that we settle on a better naming scheme. I suggest the following steps:
-
Rename
source-date.html
intosource-file.html
(since this information is related to the current Markdown file). For downward compatibility until the next release, we keepsource-date.html
around and just includesource-meta.html
from there. In v8, we removesource-date.html
-
Come up with a better naming for the translation keys. The current scheme can't be generalized nicely. My proposal:
source.file.date.updated
source.file.date.created
source.file.author
(if support is added in the future)
This would also be consistent with the new name of the partial. For downard compatibility, we can keep
source.revision.date
until v8.
Nice improvement! Implemented in cee1eb4 |
Thanks again! It'll be included in the next release. |
Trying to test it, I'm getting this error:
Just added it on Material for MkDocs' own repository. |
Ah, I wouldn't have found that without running it on a large project. There are 2 creation dates: one when you created the Will make a fix and release soon. |
OK, I released a new version (v0.9.2) that addresses this. I haven't tried building
Not sure if that's an actual error, or me not having installed |
@Stanzilla Thnx, but that PR will break compatiblity:
That's why I went for this approach: |
I changed
to
And that works for me. PR: #2629 |
Closes #2551