Error handling, .catch...

Open
  • Is something wrong?
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Start by reading server.js, the only entry point named in the issue, and trace where request errors currently reach the server. The remaining work is to define the .catch behavior and a final catch-all; done means both unchecked items are handled consistently, while the custom “Sorry” messages remain as already completed.

Written by the indexing model from the issue text.

Description

E2
  • .catch
  • Customise "Sorry" messages
  • final catch-all in server.js
Dominant language
JavaScript
Stars
2
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 fac22/week3-BDJS

All issues in fac22/week3-BDJS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.