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

[FEAT-API/UI]: Error Handling - no 500 messages on the frontend

Open
  • Is something wrong?
#755 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
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
api, frontend

Research direction

Start by locating the frontend notification handling for the “Network Error 500” message and the API error-response path. Trace how server errors reach the UI, then confirm that users receive a readable formatted error, useful API error details, or a generic retry message as the fallback.

Written by the indexing model from the issue text.

Description

The user shoudl never see a notification with: "Network Error 500". The notification should either have:

  • Specifically formatted nice to read error
  • Error logs from the API
  • A generic message to try again as the last fallback
Dominant language
No language data
Stars
2
Forks
0
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 USACE/chart-docs

All issues in USACE/chart-docs

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.