maplibre / maplibre/maplibre-react-native
Unify Error Handling
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 124
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 30
Description
Initiated from https://github.com/maplibre/maplibre-react-native/pull/828#pullrequestreview-2894201665
We should align the error throwing all around the library. We should look at these:
- `reject`
- `RCTLogError`
- MLRNLogger?
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 with the discussion linked from pull request 828, then search the library for reject, RCTLogError, and MLRNLogger to map the existing error paths. Done means the library uses a consistent error-handling approach across those paths, with the chosen behavior confirmed against the review discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100