Supported Hecate Version
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Much like HecateJS will automatically perform Auth Rules checking to determine if additional credentials are required, the library should also perform a "supported version check" to ensure that the Hecate version that it is accessing is at or above the currently supported version.
This version can be found via the `GET /api` call
cc/ @mapbox/search
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 tracing the library's Hecate request and Auth Rules flow, then inspect the GET /api response where the Hecate version is exposed. Determine how the currently supported version is defined and how an older version should be handled; the work is done when that check consistently covers connections to unsupported Hecate versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100