laravel

Laravel's pluck() method just got more powerful with closure support for both key and value parameters. No more switching to mapWithKeys() when you need simple formatting transformations. From Verbose mapWithKeys to Clean pluck Previously, when you needed to apply formatting or transformations while plucking values, you had to

Working with config arrays as collections in Laravel used to require the verbose collect(Config::array()) pattern. The new collection() method streamlines this into a single, clean call. From Nested Calls to Direct Access Previously, when you needed to use Laravel's powerful collection methods on configuration arrays, you

The Fluent class in Laravel now implements the Iterable contract, eliminating the need for toArray() calls in foreach loops. It's a small change that makes a big difference in code cleanliness. From Verbose to Natural Previously, iterating over Fluent objects required an explicit toArray() call, which felt unnecessary

Laravel's ThrottlesExceptions middleware just gained a powerful new companion with the failWhen() method. Now you can mark jobs as failed instead of just deleting them, giving you better control over job chain behavior. The Gap Between Deleting and Failing Jobs Previously, the ThrottlesExceptions middleware offered the deleteWhen() method

String validation logic in Laravel often required negating startsWith() and endsWith() calls, leading to less readable conditions. The new doesntStartWith() and doesntEndWith() methods flip this pattern for better code clarity. From Awkward Negations to Expressive Methods Previously, checking if a string didn't start or end with certain patterns

Laravel's Context API just got smarter with remember() and rememberHidden() functions that eliminate the need for manual has-get-set patterns. These new methods streamline context management with elegant closure-based caching. From Verbose Conditionals to Clean Closures Previously, managing context values required verbose conditional logic to check existence, retrieve values,

Custom Eloquent query builders in Laravel used to require overriding the newEloquentBuilder method on every model. The new UseEloquentBuilder attribute makes this relationship explicit and eliminates boilerplate code. The Old Override Pattern vs. The New Attribute Approach Previously, registering a custom query builder meant adding a method override to your

HTTP exception messages in Laravel get automatically truncated to prevent log bloat, but this can hide crucial debugging information. New truncation controls let you adjust this behavior globally or per-request. Understanding the Default Behavior Laravel automatically truncates RequestException messages to 120 characters when logging or reporting errors. This prevents your

Ever needed to use a different policy than Laravel's naming convention suggests, or wanted to make policy assignments crystal clear in your codebase? The UsePolicy attribute solves both challenges elegantly. Convention vs. Explicit Declaration Laravel's policy auto-discovery follows a simple naming convention: a Post model automatically

Laravel's make:job command now includes a --batched option that automatically scaffolds everything you need for job batching. Gone are the days of remembering which traits to import and which methods to implement. The Old Manual Process vs. The New Streamlined Approach Previously, setting up a batchable job