Closed ghost closed 7 years ago
I don't think we should print on encountering a bad date, as it's not something a package user can easily disable. Perhaps instead we have a DateValid
field, which we set to true
on success.
That's a good point, I will add this.
@SlyMarbo Please take look at the new DateValid
field.
Great stuff
Sadly, there are feeds out there that do not follow the standard. Often I encouter unparsable
date
orpubDate
elements:I've decided to not accept such dates that do not follow the RFCs but to drop them.
This PR changes the behaviour and does not not stop parsing of such a feed. Instead the default value of
0001-01-01 00:00:00 +0000 UTC
is used.