Respect timezone even in last modified date when timeZone
was set
#249
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
This PR stops forcefully converting the last modified date into UTC to respect Hugo's
timeZone
configuration.As described in #249 (comment), I understand this will be a breaking change. If we should keep backward compatibility, I will open another PR to introduce
params.forceUTCInLastMod
(key name is subject to discuss).Test plan
No particular test plan because the change is small. I checked in my local as below:
config.yaml
:Then, rendered fotter was:
Closing issues
closes #248