When element cannot be draw, no useful error is logged
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 380
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/mapbox/leaflet-image/blob/gh-pages/leaflet-image.js#L194
- The actual error isn't logged to console.
- The error is caught and logged, but I have no way of telling that programmatically - it would be great if the callback were called with the error.
- This is logged when there is an error in the callback too!
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 at leaflet-image.js line 194 and inspect the error handling around the draw failure and callback. Determine how the original error can be exposed to the caller without treating errors raised inside the callback as the draw error. Done means the actual error is useful in the console, callers can receive it programmatically, and callback errors are not misreported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100