Add endDate to events #446
No reviewers
Labels
No Label
a11y
Backlog
Blocked
Bug
Content
Dependencies
Design
Feature Request
Good First Issue
In Progress
Performance
Priority - High
Priority - Low
Priority - Medium
Untriaged
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: www/www-new#446
Loading…
Reference in New Issue
No description provided.
Delete Branch "events-end-time"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #406 and Closes #424
Usage:
Add an (optional) "endDate" property to an event's markdown file in order to add an end date to that event.
Staging:
https://csclub.uwaterloo.ca/~a3thakra/csc/events-end-time/
Older discussion happend in:
#434
Note: I have temporarily reverted the commits that change the older events to allow for code review. A few wierd artifcats are present from that in some of the event .md files, please ignore those, after unreverting before merging those will all be sorted out.
Added end time to events.to Add endDate to events@ -38,3 +39,4 @@
online,
registerLink,
permaLink,
endDate,
NIT: For readability purposes, it'd be nice to have
endDate
next tostartDate
- this would also match the order used in the Props interface and in other files. 🙂@ -27,3 +28,4 @@
year,
term,
slug,
endDate,
NIT: same as above
@ -15,3 +15,3 @@
Registration is not required to attend! We’ll just be sending you an email reminder, as well as inviting you to our calendar event.
📅 Event Date: Tuesday, September 14th from 7:00-8:30 pm ET via [Twitch](https://www.twitch.tv/uwcsclub) and [Discord](https://discord.gg/pHfYBCg)
📅 Event startDate: Tuesday, September 14th from 7:00-8:30 pm ET via [Twitch](https://www.twitch.tv/uwcsclub) and [Discord](https://discord.gg/pHfYBCg)
Just want to confirm that this and other similar occurrences will be fixed once we unrevert?
Yep it will be fixed after the revert, this commit was to fix the slight oversight on my part... I think I reverted in the wrong order which is why its a bit wierd now.
@ -7,1 +7,4 @@
/*
Note:
This script will not work for events by default anymore, since events now have startDate instead of endDate
Do we think it's worth updating the script to reflect the newly named
startDate
/endDate
fields?It looks to me like this was a one-time use script, so it shouldn't be a big deal, but it also probably wouldn't be very difficult to update the script so it still works in case we ever need to use it again.
The reason I did not fix it is that the news system is still using the old start date, so this script works for that. So whoever ends up using it in the future should fix it if they need to work with events, but not news.
Left a couple of comments, but otherwise LGTM! When unreverting, just double check to make sure that
and then this should be good to merge! 🚢