Laravel Tip: Simplify your code by leveraging Eloquent’s relationship method.
Cleaners, more expressive, and works with any “belongs to” relationship.
#php #laravel #laraveldeveloper #laraveltipstricks

Welcome to PHP Dev, a dedicated space for sharing knowledge about PHP and its ecosystem (only PHP directly related).
Help us find good articles and blogposts and provide links. Upvote or downvote, after reading, it's essential

PHP Dev

Leverage Eloquent's relationship method in Laravel to simplify your code. This approach is cleaner, more expressive, and compatible with any 'belongs to' relationship.

Laravel Tip - PHP

How do these two queries stack up in terms of expense? Have you run any metrics in Clockwork to compare? I would assume that forcing eloquent to do an extra lookup to satisfy the relationship will have a negative impact on performance.
I always say, unless it’s a positive impact for user experience and not just for developer semantics, you shouldn’t trade performance for anything.

After conducting a brief benchmark by running both the old and new methods 1000 times, they are practically indistinguishable. Surprisingly, the new method even outperformed the old one for some reason.
Nevertheless, I personally favor the old approach. While the new approach may appear cleaner, someone familiar with non-Laravel environments would easily comprehend the old version at first glance, whereas the new version would require some additional thinking. However, this is just my perspective.
<img src="https://media.daily.dev/image/upload/s---y85MArL--/f_auto/v1722037893/ugc/content_e4638ac7-c895-4a3b-b90b-24c013691bdb" alt="image">

the first one looks simple for me