First party types
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 768
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
It's 2024, and this project still expects users to trust the community maintained types, taking on the risk of type drifting from the official repo. Mapbox has revenue of many, many million dollars, and yet this remains the case. why?
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, entry points, or acceptance criteria are named. Start by reviewing how this JavaScript SDK currently obtains or publishes its types and compare that with the official repository's available type information. Done would require an agreed first-party type source and a defined way to keep it aligned with the SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100