lyqht/Octokit-lite

Add Error Boundary for handling request errors

Open

#10 opened on Sep 30, 2022

View on GitHubContributor guide
 (13 comments) (0 reactions) (0 assignees)TypeScript (11 forks)auto 404
good first issue

Repository metrics

Stars
 (17 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

In both Unfork and TopicSpace, there is no error handling of showing error notification/popup in the case when the network request to API routes fails e.g. in the case of bulk repository delete (#3) or other edge cases.

Suggested Solution

Add a React error boundary to catch all network errors and display it as a simple error popup ui at the right top edge of the app.

Contributor guide

Research direction
Identify the root component where an error boundary can be placed. Use React's ErrorBoundary pattern to catch network errors and display a toast notification at the top right of the app.
Tech stack
typescriptreact
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75