You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The column that shows the date for failed jobs (and also some other locations in the app) is sometimes ambiguous.
For example, lets assume it's January 2020. You have an app that doesn't get many failed jobs. But when you look at the table in mid January look you see this:
On first glance it's hard to know if this job failed on 19th Jan 2020 or 20th Jan 2019.
Having a 2 digit number for the year is not enough IMO.
I see this this format is forced in the following method:
@jonnywilliamson, If you submit a PR, would you add a config option that supports editing the default format, instead of hard-coding a format? This would allow a user to define a relative format, or add a day of the week, etc.
The column that shows the date for failed jobs (and also some other locations in the app) is sometimes ambiguous.
For example, lets assume it's January 2020. You have an app that doesn't get many failed jobs. But when you look at the table in mid January look you see this:
On first glance it's hard to know if this job failed on 19th Jan 2020 or 20th Jan 2019.
Having a 2 digit number for the year is not enough IMO.
I see this this format is forced in the following method:
horizon/resources/js/base.js
Lines 86 to 88 in 11acb6e
Would a PR be accepted to change this to
YYYY
instead?Thanks.
The text was updated successfully, but these errors were encountered: