gleam-lang/gleam
View on GitHubOffer to create an API token if the Hex API rate limit is set
Open
#2,584 opened on Feb 7, 2024
3 comments (3 comments)0 reactions (0 reactions)0 assignees (0 assignees)Rust21,417 stars (21,417 stars)960 forks (960 forks)batch import
help wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- rust
- Domain
- developer experiencetooling
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- fresh
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- basic Rust knowledgeunderstanding of Hex API
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- Investigate the Gleam compiler's interaction with the Hex API, specifically how API requests are made and rate limit responses are handled. Look for relevant code in the compiler's source (e.g., in the `hex` module). Determine where to intercept a 429 status and provide a suggestion to create an API token. Review any existing comments on this issue for additional context.