Livewire Code Review: Likeable Component - 10 Improvements

This is a code review of a Livewire component, which is actually optimization of the PHP class. Will you join me?
00:00 Introducing Component
01:31 Code Overview
03:01 Undefined Class Properties
03:51 Dynamic Class Names
05:45 Unnecessary Variable/Query
07:30 Formatting the Code
07:47 Config Default Values
09:15 Public or Private Methods
10:40 Wait, THAT many DB Queries??
15:17 Remove Duplicate Methods
15:57 Eloquent create() vs save()
17:07 Remove Even More Methods
Related links:
- Laravel and PHP Try-Catch: Exceptions VS Errors? • Laravel and PHP Try-Ca...
- My Course "Practical Laravel Livewire from Scratch" laraveldaily.teachable.com/p/...
- My Livewire Kit: Set of Components livewirekit.com/
- - - - -
Support the channel by checking out our products:
- Enroll in my Laravel courses: laraveldaily.teachable.com
- Try our Laravel QuickAdminPanel: bit.ly/quickadminpanel
- Purchase my Livewire Kit: livewirekit.com
- View Laravel Code Examples: laravelexamples.com
- Subscribe to my weekly newsletter: bit.ly/laravel-newsletter

[@daleryanaldover6545]

I found out about using dynamic class names by source diving the Model class. Another cool thing you can do is using dynamic variable names which is kinda weird but helps if you found yourself in a scenario where dynamic variables would be helpful.

[@ilhamfajriumar9085]

I think setting up the initial like or dislike is the best way to reduce the query even more, that's the way i did it in some of my project

[@maximusmitchell1229]

How do you mean?

[@ilhamfajriumar9085]

When the likeable component loading it's actually getting the like status inside mount. If there are multiple likeable component loaded the query will run as much as the loaded components. Instead doing that, passing the like status from parent component, which can be fetched using eager loading will reduce the query thats being called

[@rahmanramsi]

I prefer to pass the model itself instead only the classname and id, so i dont need to query to database to get the data, cuz its already there. So it should becomes like this `@livewire('likeable', ['model' => $comment])

[@nabilhassen1944]

its not secure to do so. anyone can open up the devtools and all of your model data will be available there.

[@rahmanramsi]

@@nabilhassen1944 didn't know that, thanks for the info.

[@rahmanramsi]

@@nabilhassen1944 btw where i can find that model data in devtool?

[@usanzadunje]

14:50 Could we just query all the likes(that we need of course) from the parent component and then pass them to each button component. This would result in only one query and remove query to db from component itself?

[@LaravelDaily]

Yes, probably, but that kinda defeats the purpose of component that could be reused anywhere.

[@krishnanarasimha1243]

I missed the yesterday 48 hour videos :(

[@kingstalker]

King Stalker 0 seconds ago Is there anyway to make the blade syntaxes autocomplete for you for the live wire things also can it not look so white I see spatie permissions blade does the same thing for example I say @role(autocomete your role ) and looks like a normal blade syntax I hope I make sense

[@LaravelDaily]

Some Blade support comes from PhpStorm, some can be provided by Laravel Idea package for PhpStorm, but I don't think they cover specific packages like Spatie Permissions or others.

[@Ghost-hz2dy]

In the next video "code review" i want to share my github repository and review it. How i can send you email ?

[@LaravelDaily]

Currently I have 5 reviews in queue, so realistically I can do only in November. You can email me [e-mail] and invite me to GitHub, username povilaskorop

[@abdulrehmandar8541]

I have a question. 1. livewire always render full page on request. Is there any way to render only specific div. without using wire:ignore. 2. I have a bootstrap form wizard when ever make some request the wizard steps become inactive or may go to first step if we are on other step. currently i'm handling it making the steps dynamic to check which step is active or not it works but still flicker. do you have any idea, advice to manage state. Thank you.

[@LaravelDaily]

1. No, unless you split them into separate components 2. Can't answer in a comment, needs debugging

[@ahmednisar9960]

make one laravel project from scratch....not like this