mapbox / mapbox/github-org-browser
Better error handling and meaningful error messages
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently if something bad happens, you won't see ant error.
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
No files, failing cases, or entry points are identified. Start by reproducing failures in github-org-browser and tracing the JavaScript error paths; done means failures are surfaced with meaningful messages instead of being silent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100