Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

TV Show Project Level 300: Swap back to your old codebase

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start with episodes.js and the existing getAllEpisodes flow, then review how the website consumes episode data for searching, scrolling, and selection. Read the TVMaze episode-list API documentation and test the loading and simulated-error states. Done means episodes.js is removed, the URL is fetched once per visit, and users receive visible waiting or error feedback.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 📅 Sprint 2 Core Submit:None

Level 300

For level 300, you should switch back to your original codebase.

You should have reviewed and merged your partner's level 200 changes through a PR to your own repo.

Remember to pull the latest changes onto your local machine.

Once again, compare their implementation to yours. Think:

  1. How is it different?
  2. What do you prefer about your implementation?
  3. What do you prefer about their implementation?
  4. What did you learn that you didn't know before?

Have a discussion about your answers to these questions. In class, together, give a 3 minute talk about your conclusions.

Refactoring

Like with level 200, feel free to change anything in your codebase which you think will make it easier to work with, or to build new features.

Make a branch and pull request for yourself, and then have your partner review, making sure they understand the changes made.

Adding new functionality

Level 300 is about getting rid of our static data from episodes.js, and instead using an API.

Requirements
  1. You must delete the episodes.js file from your repository.
  2. Your website must still work the same, but by using a fetch request to https://api.tvmaze.com/shows/82/episodes. This URL should serve the exact same content as was returned by getAllEpisodes in episodes.js.
  3. You must fetch this URL only once per visit to your website. You should not re-fetch when someone searches, scrolls, or selects an episode from the drop-down.
  4. If you don't have data yet, you should show something to tell the user to wait for the data.
  5. If an error occurred loading the data, notify the user.
  6. Note: real users don't look in the console - console.log or console.error are not sufficient for this requirement.
  7. You will need to simulate an error to test this out yourself.
Documentation

You can see that this endpoint has been documented here: https://www.tvmaze.com/api#show-episode-list

Dominant language
JavaScript
Stars
0
Forks
276
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from CodeYourFuture/Module-Data-Flows

All issues in CodeYourFuture/Module-Data-Flows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.