search

coleslaw-org / coleslaw

Flexible Lisp Blogware
BSD 2-Clause "Simplified" License
553 stars 82 forks source link

Silent misbehaviour: bad date formatting #172

Closed equwal closed 4 years ago

equwal commented 5 years ago

If you use a date like date: 2019-4-28 instead of date: 2019-04-28, coleslaw will silently make that date the same as 2019-40-28.

It would be nice if coleslaw threw an error instead. With coleslaw-mode you can have your date inserted by itself, so I found this on one of my old posts where I interted it manually.

PuercoPop commented 5 years ago

Hey, I can't reproduce the issue. If I use 2019-4-28 as the date I get 2019-4-28. parse-metadata doesn't try to massage the data and the template functions writes the date as is.

Could you post more specific reproduction instructions?

equwal commented 5 years ago

Sure: Make a coleselaw repo Make two files Make one date: 2019-4-28 post Make another have date: 2019-04-29 Deploy Look at the index, the 2019-4-28 should be above (more recent) than 2019-04-28.

guicho271828 commented 4 years ago

So it is not like the date is actually formatted as 2019-40-28 , but merely ordered in a weird manner?

equwal commented 4 years ago

Sorry for having been imprecise.

What I mean

So it is not like the date is actually formatted as 2019-40-28 , but merely ordered in a weird manner?

Sorry for having been imprecise earlier.

This is what I mean, that in the index pages, when sorted by date, the order of the blog posts is off.

equwal commented 4 years ago

I'm no longer convinced this issue is worth the effort to try to fix.