Open
Description
Emoji symbol
⏸️
Emoji code
⏸️
Emoji description
Added/updated rate-limiting
Describe the use case of your emoji
There's currently no well-fitting Gitmoji to indicate that rate-limiting was introduced or changed. Almost all servers that expose APIs limit the number of requests that each client can make per time interval, in order to avoid being slowed down and to ensure that allhe other clients are served fairly. Furthermore, clients frequently decide to rate-limit themselves (e.g. using a task scheduler) to avoid being banned by the API server.
In other words, as a use case, rate-limiting is probably as common as multi-threading.
- ✨ doesn't fit because rate-limiting is not really a “feature”
- ⚡️ doesn't fit because performance doesn't have that much to do with rate-limiting
- ♻️ is too generic and doesn't cover adding rate limits
- 🏗️ doesn't fit because rate-limiting isn't (a type of) architecture
- 🧵 doesn't fit because rate-limiting doesn't imply multi-threading (rate-limiting is perfectly possible on a single thread)
Is this use case covered by an existing emoji?
No ❌
Does this emoji fall into the "how" or the "what" category?
- This proposal do not describe "how" a commit was made, but does in fact describe "what" is the contents of the commit about.
Examples
- ⏸️ Add rate-limiting to /account API
- ⏸️ Make rate limit stricter
- ⏸️ Login page: Allow only 6 requests per minute
- ⏸️ Rate-limit per access token, not per endpoint
- ⏸️ Self-limit FeedFetcher (avoid DoS-ing)
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue requesting the emoji.