Closed JasonSwindle closed 4 years ago
Offending line: https://github.com/kickscondor/fraidyscrape/blob/master/index.js#L117
Example non-working string: Wed, 11 Mar 2020 10:22:12 EET
Example working string: Wed, 11 Mar 2020 04:00:00 -0000
Core issue: RSS feed pubdate allows RFC 822 DateTime formatting, Javascript Date.Parse supports ISO 8601.
My recommendation would be to use Moment
to handle parsing, but if you don't want that to be a dependency, you will have to either copy what they do for this or build your own 'Timezone Shorthand to -0000
-formatted string converter'
Edit: to expand, this might be a localization issue with the browser's implementation of Date.parse
- because Wed, 11 Mar 2020 10:22:12 PST
works just fine for me, while the EET
version does not, even though they are both valid timezones.
Ok, good - thank you for the suggestions. And thank you for doing the homework to track this down! You're dead on.
This turned out to be unknown time zones - a fix is in Fraidyscrape 1.0.4.
I'm still seeing everything listed as 50Y. Is the Fraidyscrape 1.0.4 fix in 1.13?
I'm sorry - I meant 1.1.4, still wrapping it up.
Desktop (please complete the following information):
Describe the bug FraidyCat thinks the last update for GOG was 50 years ago (LOL), and does not seem to order post correctly either.
FraidyCat
RSS