Server response codes / error-handling

Open
  • Is something wrong?
#144 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
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
api, backend

Research direction

Start by locating the server request handlers and the utility functions used for error cases. Trace how validation failures and other errors reach the client or browser, then compare the current responses with the issue's requirement for appropriate non-200 response codes. Done means failed requests are distinguishable by their response codes and invalid input is handled consistently.

Written by the indexing model from the issue text.

Description

server

It doesn't look like you are doing much input validation in the server or returning appropriate response codes in case of errors.

Having the util functions to handle error cases is really good but I think they'll always return a 200 OK so it's difficult for your client/browsers to handle failed requests properly.

Dominant language
JavaScript
Stars
4
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 fac-14/OSCEBossKey

All issues in fac-14/OSCEBossKey

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.