Api Error Handling

Open
#22 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
react, typescript
Domain
api, authentication, frontend

Research direction

No files or tests are named. Start by locating the API request and authentication entry points in the React application, then trace how 403, 404, 500, expired tokens, and user-facing alerts are currently handled. Done means the project has an agreed behavior for each listed case and verifies those behaviors.

Written by the indexing model from the issue text.

Description

  • 403 Forbidden
  • 404 Not Found
  • 500 Server Error
  • Access token Expire
  • Pop Up alert vs notification vs Bug report (bugsnag)
Dominant language
TypeScript
Stars
23
Forks
9
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 ml-opensource/admin-panel-template-reactjs

All issues in ml-opensource/admin-panel-template-reactjs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.