make a breaking change to swap to lon/lat order
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 674
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
For consistency with GeoJSON, GL JS we should bump the major version number and swap to lon/lat order.
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 reviewing the library's public encoding and decoding entry points and comparing their current coordinate order with the GeoJSON and GL JS conventions named in the issue. Done means the API consistently uses lon/lat order, the major version bump is accounted for, and the compatibility impact is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100