HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
thejsj
calendar-exercise
JavaScript2016–2016
thejsj / calendar-exercise

calendar-exercise

An calendar app built on React.js. Uses a graph algorithm to display events.

2Distinct people
2Mentions
0Explicit recommenders
2GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An calendar app built on React.js. Uses a graph algorithm to display events.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2016-04-08 04:58:11 UTC to 2016-04-08 23:29:13 UTC.

012016-04-08 04:00:00 UTC to 2016-04-08 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 8, 04:002016-04-08 05:00:00 UTC to 2016-04-08 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 06:00:00 UTC to 2016-04-08 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 07:00:00 UTC to 2016-04-08 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 08:00:00 UTC to 2016-04-08 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 09:00:00 UTC to 2016-04-08 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 10:00:00 UTC to 2016-04-08 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 11:00:00 UTC to 2016-04-08 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 12:00:00 UTC to 2016-04-08 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 13:00:00 UTC to 2016-04-08 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 8, 13:002016-04-08 14:00:00 UTC to 2016-04-08 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 15:00:00 UTC to 2016-04-08 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 16:00:00 UTC to 2016-04-08 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 17:00:00 UTC to 2016-04-08 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 18:00:00 UTC to 2016-04-08 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 19:00:00 UTC to 2016-04-08 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 20:00:00 UTC to 2016-04-08 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 21:00:00 UTC to 2016-04-08 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 22:00:00 UTC to 2016-04-08 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-08 23:00:00 UTC to 2016-04-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 8, 23:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 8, 04:002016-04-08 04:00:00 UTC2016-04-08 05:00:00 UTC101
Apr 8, 05:002016-04-08 05:00:00 UTC2016-04-08 06:00:00 UTC000
Apr 8, 06:002016-04-08 06:00:00 UTC2016-04-08 07:00:00 UTC000
Apr 8, 07:002016-04-08 07:00:00 UTC2016-04-08 08:00:00 UTC000
Apr 8, 08:002016-04-08 08:00:00 UTC2016-04-08 09:00:00 UTC000
Apr 8, 09:002016-04-08 09:00:00 UTC2016-04-08 10:00:00 UTC000
Apr 8, 10:002016-04-08 10:00:00 UTC2016-04-08 11:00:00 UTC000
Apr 8, 11:002016-04-08 11:00:00 UTC2016-04-08 12:00:00 UTC000
Apr 8, 12:002016-04-08 12:00:00 UTC2016-04-08 13:00:00 UTC000
Apr 8, 13:002016-04-08 13:00:00 UTC2016-04-08 14:00:00 UTC000
Apr 8, 14:002016-04-08 14:00:00 UTC2016-04-08 15:00:00 UTC000
Apr 8, 15:002016-04-08 15:00:00 UTC2016-04-08 16:00:00 UTC000
Apr 8, 16:002016-04-08 16:00:00 UTC2016-04-08 17:00:00 UTC000
Apr 8, 17:002016-04-08 17:00:00 UTC2016-04-08 18:00:00 UTC000
Apr 8, 18:002016-04-08 18:00:00 UTC2016-04-08 19:00:00 UTC000
Apr 8, 19:002016-04-08 19:00:00 UTC2016-04-08 20:00:00 UTC000
Apr 8, 20:002016-04-08 20:00:00 UTC2016-04-08 21:00:00 UTC000
Apr 8, 21:002016-04-08 21:00:00 UTC2016-04-08 22:00:00 UTC000
Apr 8, 22:002016-04-08 22:00:00 UTC2016-04-08 23:00:00 UTC000
Apr 8, 23:002016-04-08 23:00:00 UTC2016-04-09 00:00:00 UTC101

What Hacker News says

2 sources
I am not from Facebook, but I read through your tests and found one that violates the problem description on line 74 of test/index.js. The first statement of the problem is, "If two events collide in time, they MUST have the same width." So a width of 2/3 is not possible, all widths must have a numerator of 1. This rule is important because it makes the widths of the events deterministic, which otherwise they are not. That same test illustrates this exact problem, why not have the widths be 1/2, 1/4, 1/4, 1/2? Considering the first constraint the correct layout is all having width 1/3. https://github.com/thejsj/calendar-exercise/blob/master/test...
In Ask HN: How do detect a crappy boss / toxic environment when interviewing?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.