USRSE / USRSE/usrse.github.io

Implement "Add to Calendar" for Repeated Events

Open
#558 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

design hacktoberfest
Dominant language
HTML
Stars
33
Forks
104
Avg merge
12h 3m
Merged PRs (30d)
10

Description

Currently, the add to calendar button can work easily for a non-repeated event because we have a reliable date and time from the event markdown directly. Repeated events are generated by the fullcalendar plugin so we don't have this, so we can't populate the javascript call. A solution to this problem would (I think) be able to associate the date from the calendar with a link to the page, possibly as a GET variable, and then have the page read it into the calendar button login. In other words, here is how I would do this:

  1. Figure out how to get the actual (calculated) date time for an event, and add it to a data attribute somewhere
  2. Hijack the event on click (event.preventDefault) and retrieve this value, add it to the url that would have been clicked
  3. On the event page, retrieve the variable from the GET and use it to populate the add to calendar button.

Done!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the FullCalendar integration, the repeated-event link handling, and the event-page add-to-calendar button. Trace how a calculated occurrence date can travel from the calendar click to the event page, then verify that the button uses that date for repeated events without breaking non-repeated events.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.