Provide more information about errors in mapbox
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
Right now, If there is an error, Mapbox will throw an error with an error message. There is no way to programmatically check the type of error and if the error is related to a layer, a style expression , ...etc.
It will be nice to have error type and metadata associated with the error so that the host application will be able to handle error better.
Background:
Given an application that allows the user to load layers from different sources, if a layer filter fails, The application should be able to know the type error and the action that caused so that it can remove the problematic error.
## Design Alternatives
## Design
### Mock-Up
### Concepts
### Implementation
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, tests, or entry points are named. Start by reviewing how mapbox-gl-js currently reports errors and how applications receive them, then determine the error categories and metadata needed for layer and style-expression failures. Done means an agreed design and implementation scope, including how hosts can identify the error type and triggering action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100