codefordenver / codefordenver/code-for-denver-site

Handle case where the CFAPI fails to load properly

Open
#281 0 comments 0 reactions 0 assignees View on GitHub
best practice ready UX
Dominant language
JavaScript
Stars
11
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Currently the next event section shows the epoc.

![](https://fd-files-production.s3.amazonaws.com/79159/ejcoBRU-LWsLbKAdLSL6NQ?X-Amz-Expires=300&X-Amz-Date=20160629T040241Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIA2QBI5WP5HA3ZEA/20160629/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=d5c55f836f34e81b8b569c20b6c5a8166cde43300b8216931f82a5464a6655fe)

Contributor guide

Open the contributing guide

Research direction

Start by locating the next event section and the code that loads data from the CFAPI. Reproduce the failed-load case shown in the issue and trace how the epoch value reaches the display; done means the section handles the failure without showing an epoch, with the expected fallback behavior verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.