this is promising , just a feedback ( i'm not trying to be rude 😅 ) if taylor gives the "what's new in laravel" episodes because Mohammed here has it hard pronouncing words correctly , it would be better for Mohammed to do an arabic version of "what's new in laravel" episodes keep up the good work
whereBelongsTo: In that situation I'd do $posts = $category->posts()->get() for the same functionality (assuming the hasMany relationship is defined and isn't loaded yet). It does look useful when you add the ability to use it multiple times. And it does look nicer when your query starts with the Model class instead of a variable. LazilyRefreshDatabase: Nice. reduceMany: I use reduce a lot. This will come in handy. @aware: I don't write components that much but it looks really good.
I thought that the LazilyRefreshDatabase was implemented with database Transaction; which means that it won't work well if a test contain sql such as truncate. In which case DatabaseMigration trait is useful. If LazilyRefreshDatabase is now default how can we test code that has truncate? I have had to change truncate on a temp table to delete which is slower
Holy crap octane is fast.. just started using it on vapor and I'm super impressed. Keep up the good work.
this is promising , just a feedback ( i'm not trying to be rude 😅 ) if taylor gives the "what's new in laravel" episodes because Mohammed here has it hard pronouncing words correctly , it would be better for Mohammed to do an arabic version of "what's new in laravel" episodes
keep up the good work
whereBelongsTo: In that situation I'd do $posts = $category->posts()->get() for the same functionality (assuming the hasMany relationship is defined and isn't loaded yet). It does look useful when you add the ability to use it multiple times. And it does look nicer when your query starts with the Model class instead of a variable.
LazilyRefreshDatabase: Nice.
reduceMany: I use reduce a lot. This will come in handy.
@aware: I don't write components that much but it looks really good.
$category->posts
The commit to use the new LazilyRefreshDatabase trait in the default TestCase was reverted by Taylor in PR #5700 in the laravel/laravel repository.
I thought that the LazilyRefreshDatabase was implemented with database Transaction; which means that it won't work well if a test contain sql such as truncate. In which case DatabaseMigration trait is useful. If LazilyRefreshDatabase is now default how can we test code that has truncate? I have had to change truncate on a temp table to delete which is slower
15h per day working. just want to be like you.🙂🙂
Wait is this the main laravel channel
yes
@@themsaid wowww
@aware is lit
Couple of typos in the Post::whereBelongsTo.. screenshot, Blongs should be Belongs, and ->get() should be used only once. :)
Yes I noticed 😅 sorrrry
great
Thanks a lot :)