codeforpdx / codeforpdx/recordexpungPDX
Create reusable error component
Open
Nobody has claimed this yet.
design
frontend
refactor
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 93
- Avg merge
- 8m
- Merged PRs (30d)
- 9
Description
We are currently creating error related logic on a case by case basis. It would be helpful to have one way to handle errors.
This task is done when:
- There is an error component that will replace a failing component
- The error component is connected to the store so we can move error handling into Redux/services
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing case-by-case error handling and the Redux/services integration points. Review how failing components are rendered and identify the project conventions for shared components. Done means a reusable error component can replace a failing component and is connected to the store for centralized error handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100