feat: Add #[Throttle] Attribute for Rate Limiting#206
Merged
techmahedy merged 1 commit intodoppar:3.xfrom Mar 5, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new
#[Throttle]attribute for declarative rate limiting on controller methods, providing a modern alternative to docblock annotations and route-level rate limit parameters.Currently, Doppar supports rate limiting through:
@RateLimit 60/1#[Route('/api/users', rateLimit: 60)]This PR introduces a new
#[Throttle]attribute for declarative rate limiting on controller methods.Before (Docblock Annotation)
Before (Route Attribute Parameter)
Before (With Middleware)
After (New #[Throttle] Attribute)
Result: 10 requests per minute
In a future major version, we may deprecate docblock annotations and route parameters in favor of attributes.