Releases: alisaifee/flask-limiter
Releases · alisaifee/flask-limiter
3.1.0
Feature
- Skip logging an error if a decorated limit uses a callable
to return the "current" rate limit and returns an empty string.
Treat this is a signal that the rate limit should be skipped for
this request.
3.0.0b2
Breaking changes
- Remove deprecated config variable RATELIMIT_STORAGE_URL
- Remove legacy backward compatibility path for flask < 2
- Enforce key_func as a required argument
Chores
- Simplify registration of decorated function & blueprint limits
3.0.0
Breaking changes
- Change order of extension constructor arguments to only require
key_func
as the first positional argument and all other arguments
as keyword arguments. - Separate positional/keyword arguments in limit/shared_limit decorators
- Remove deprecated config variable RATELIMIT_STORAGE_URL
- Remove legacy backward compatibility path for flask < 2
Features
- Allow scoping regular limit decorators / context managers
3.0.0b1
Breaking changes
- Change order of extension constructor arguments to only require
key_func
as the first positional argument and all other arguments
as keyword arguments. - Separate positional/keyword arguments in limit/shared_limit decorators
Features
- Allow scoping regular limit decorators / context managers
2.9.2
Feature
- Extend customization by http method to shared_limit decorator
2.9.1
Chores
- Update documentation quick start
- Refresh documentation for class based views
2.9.0
Features
- Allow using
limit
&shared_limit
decorators on pure
functions that are not decorated as routes. The functions
when called from within a request context will get rate limited. - Allow using
limit
as a context manager to rate limit a code block
explicitly within a request
Chores
- Updated development dependencies
- Fix error running tests depending on docker locally
- Update internals to use dataclasses
2.8.1
Chores
- Add sponsorship banner to rtd
- Update documentation dependencies
2.8.0
Breaking changes
- Any exception raised when calling an
on_breach
callback will
be re-raised instead of being absorbed unlessswallow_errors
is set.
In the case ofswallow_errors
the exception will now be logged
atERROR
level instead ofWARN
- Reduce log level of rate limit exceeded log messages to
INFO