Parse all RSS and ATOM dates permissively #56
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The existing FeedKit code is pretty strict about date formats, so quite possibly you'll be horrified by the very idea of this patch. Nevertheless, I do see quite a few ISO-format dates showing up in RSS feeds.
This patch liberalizes XML date parsing by attempting RFC822, RFC3339, and ISO8601 decoding on every date field rather than limiting each field to its specified format. RFC822 is different enough, and the other two are similar enough, that there should be no difference in the result except that some dates that were previously rejected will now be interpreted correctly.