-
-
Notifications
You must be signed in to change notification settings - Fork 475
Add human-readable date field to all-events.json #1729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Added a humanReadableDate field to each event in all-events.json to match the format used in all-cfps.json. This provides an easy-to-read date string (e.g., "May-15-2017" or "April-25-2017 - April-28-2017") alongside the existing timestamp arrays. Changes: - Added formatDateHumanReadable() helper function to convert timestamps - Updated event object generation to include humanReadableDate field - Single-day events show as "Month-Day-Year" - Multi-day events show as "Month-Day-Year - Month-Day-Year" 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
|
|
||
| const getTimeStamp = (year,month,day) => new Date(Date.UTC(year,month,day,0,0,0)).getTime() | ||
|
|
||
| const formatDateHumanReadable = (timestamp) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@scraly what do you think about the human readable format to use? we can go more humans readable here, and probably in the cfp generation too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does the humanreadable data can cause troubles about the dates cause by timezones?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the CFP it could, but in the event dates it is always local time respect to the event location.
|
About this draft feature I have a question: why? :) |
|
@scraly This is a draft because I wanted to double-check whether the new human-readable format is good enough or if we want to use a specific one. |
|
I think it can be sufficient. |
|
Ok, let's get this in then :) |
|
Interesting, let me double check |

Summary
humanReadableDatefield to each event inall-events.jsonto match the format used inall-cfps.json"May-15-2017""April-25-2017 - April-28-2017"Changes
formatDateHumanReadable()helper function intools/mdParser.jsto convert timestamps to human-readable formathumanReadableDatefieldExample Output
{ "name": "Craft Conf", "date": [1493078400000, 1493337600000], "humanReadableDate": "April-25-2017 - April-28-2017", "hyperlink": "https://craft-conf.com/", "location": "Budapest (Hungary)", ... }Test plan
node tools/mdParser.jsto regenerateall-events.jsonhumanReadableDatefield🤖 Generated with Claude Code