For years, working with Eloquent models in Laravel meant relying heavily on configuration arrays like $fillable and $casts. They worked, and they became part of how most developers approached model design. But if we’re honest, they always felt a bit disconnected from the language itself.
They weren’t really code. They were configuration.
And over time, that distinction starts to matter.
From Configuration to Code
With modern PHP improvements — especially typed properties and a stronger type system — the way we think about models is starting to shift. Instead of describing our models through arrays, we can now express them directly using real PHP constructs.
That change might look small on the surface, but it represents a deeper evolution.
We’re moving from array-based configuration toward expressive, type-safe code. Instead of telling Laravel how to treat attributes through strings and mappings, we define intent directly in the structure of the object.
That makes models easier to read, easier to reason about, and closer to how we think about domain logic.
Why This Shift Matters
The biggest improvement is clarity. When properties are defined explicitly with types, you don’t need to mentally parse arrays to understand what a model contains or how it behaves. The structure becomes self-documenting.
Type safety also improves. Instead of relying on casting rules defined elsewhere, the language itself helps enforce correctness. This reduces subtle bugs that often appear when data doesn’t match expected formats.
Another benefit is better tooling. IDEs can understand typed properties far more effectively than dynamic arrays, which leads to better autocomplete, safer refactoring, and fewer mistakes during development.
Over time, these small improvements compound. The codebase becomes easier to maintain, especially as it grows.
A Change in Mindset
This is not just a syntactic improvement.
It’s a mindset shift.
For a long time, many Laravel developers treated models as flexible containers shaped by configuration. But modern PHP encourages a different approach — treating models as real objects with clearly defined structure and behavior.
That means being more intentional about how data is represented. It means embracing the language instead of working around it.
Where This Leads
Laravel has always evolved alongside PHP. As the language becomes more expressive and type-safe, the framework naturally moves in the same direction.
The more we lean into these changes, the more our code starts to reflect actual design instead of configuration.
And that’s a good thing.
Because in the end, the goal isn’t just to make things work.
It’s to make them clear, predictable, and maintainable.