This repository has been archived by the owner on Jul 17, 2018. It is now read-only.
Posts should support "update: now" header #49
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Note that automatic generation (#11) will make this super awesome. |
xmlschema doesn't encode fractional parts, so set_updated_time turns the Time object into a string without fractional seconds, then post.updated will be a Time object without a fractional part, so a comparison with t (which does have a fractional part) fails.
This would cause a perpetually updating post.
aprescott
added a commit
that referenced
this pull request
Mar 18, 2013
Posts should support "update: now" header
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If a published post contains an
update: nowheader, theupdatedheader should automatically be updated to the current timestamp.This allows users who want to manage content with just their files to not worry about managing timestamp information.