Тёмный

Livewire Code Review: Likeable Component - 10 Improvements 

Laravel Daily
Подписаться 145 тыс.
Просмотров 7 тыс.
50% 1

Опубликовано:

 

4 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 18   
@daleryanaldover6545
@daleryanaldover6545 3 года назад
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
@ilhamfajriumar9085 3 года назад
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
@maximusmitchell1229 3 года назад
How do you mean?
@ilhamfajriumar9085
@ilhamfajriumar9085 3 года назад
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
@rahmanramsi 3 года назад
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
@nabilhassen1944 3 года назад
its not secure to do so. anyone can open up the devtools and all of your model data will be available there.
@rahmanramsi
@rahmanramsi 3 года назад
@@nabilhassen1944 didn't know that, thanks for the info.
@rahmanramsi
@rahmanramsi 3 года назад
@@nabilhassen1944 btw where i can find that model data in devtool?
@usanzadunje
@usanzadunje 3 года назад
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
@LaravelDaily 3 года назад
Yes, probably, but that kinda defeats the purpose of component that could be reused anywhere.
@krishnanarasimha1243
@krishnanarasimha1243 3 года назад
I missed the yesterday 48 hour videos :(
@Ghost-hz2dy
@Ghost-hz2dy 3 года назад
In the next video "code review" i want to share my github repository and review it. How i can send you email ?
@LaravelDaily
@LaravelDaily 3 года назад
Currently I have 5 reviews in queue, so realistically I can do only in November. You can email me povilas@laraveldaily.com and invite me to GitHub, username povilaskorop
@kingstalker
@kingstalker 3 года назад
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
@LaravelDaily 3 года назад
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.
@abdulrehmandar8541
@abdulrehmandar8541 3 года назад
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
@LaravelDaily 3 года назад
1. No, unless you split them into separate components 2. Can't answer in a comment, needs debugging
@ahmednisar9960
@ahmednisar9960 2 года назад
make one laravel project from scratch....not like this
Далее