Laravel 10.46 Released
The Laravel team released v10.46 this week with new Enum validation methods, incrementing a rate limiter by a custom amount, Conditionable Enum validation rules, and more:
Enum Validation gets only() and except() methods
@Anton5360 contributed two new methods to the Enum validation rule when you don’t expect all enum cases to be valid:
Rule::enum(ServerStatus::class)
->only([ServerStatus::Pending, ServerStatus::Active]);
Rule::enum(ServerStatus::class)
->except([ServerStatus::New]);
A status enum is a perfect example of where these methods might be practical: after a record status moves away from New
, you’ll likely not want to allow a record to return to that status again. Another example from the pull request description is once a shipment status is shipped
, you’ll only allow delivered
, cancelled
, or rejected
.
Rate limiter may be incremented by a custom amount
Sebastien Armand contributed the ability to increment a rate limit value by a custom amount:
Sometimes a rate limit doesn't map directly to an increase of 1 at a time. Some examples would be:
- a limit on bandwidth used
- a limit on # of updates across batch calls where each call could mean multiple "hits"
- a limit on time spent on some operations
Here’s an example of how you can use the increment()
method to increase the total by a custom amount:
use Illuminate\Support\Facades\RateLimiter;
RateLimiter::increment('send-message:'.$user->id, amount: 5);
See Manually Incrementing Attempts in the documentation for details.
Conditionable added to the Enum rule
Michael Nabil contributed the ability to use the Conditionable
trait with the Rule::enum()
validation rule:
Rule::enum(PostStatus::class)
->when(
auth()->user()->is_admin,
fn ($rule) => $rule->only([PostStatus::APPROVED]),
fn ($rule) => $rule->only([PostStatus::PADDING]),
);
Release notes
You can see the complete list of new features and updates below and the diff between 10.45.0 and 10.46.0 on GitHub. The following release notes are directly from the changelog