You mean repository pattern? I'm not a big fan of it. I explained it in this free lesson of my course "How to structure Laravel project": laraveldaily.teachable.com/courses/how-to-structure-laravel-project/lectures/8760335
@@PovilasKorop I appreciate your take on repository patterns. I haven't used it so far in my projects and here I am thinking that it's the "standard" for many companies. thanks!
Hei, very helpful and good tip. I have a question about collecting views count. What are the good options for getting page/post views for laravel app and vuejs (only) app? Is this something that would be worth doing video on or mby you can comment on that?
Well, not sure what is problematic here, just in show() method of a controller you do $post->increment('views_count') or something like that. And if you have Vue app with API, then you should probably have a separate API endpoint to increase views count.
Hey there! Your videos are realyy helpful. Is there any chancee to have your courses in some kind of package? I found 3 of them what really fits my current job of refactoring, so a bundle would be nice. Keep up the good work!
Hi Gergely, I don't have a special package, but I can offer you a deal: if you buy any 2 of my courses, email me povilas@laraveldaily.com and I will assign you another one for free.
@@PovilasKorop Thanks, great! The course "How to Structure..." seems really helpful, and a question pops out already from the preview. I have to deal with an acient project (5.1, all logic in controllers, ~30 models, sad story), after refactoring new funcionality has to be added. However, accessors/mutators introduced, but no model observers in this Laravel version what I miss already. What is you opinion, to what version would be the lightest 'pain in the ...' to update? 5.3/5.8 or huge refactoring and switch to 8?
@@gram_o_phone From what I remember, the biggest structural change and biggest pain to upgrade was from 5.2 to 5.3, later not much has changed globally in the structure of Laravel project, only new functions added and relatively small changes. So depends on your budget/time, I would advise to upgrade to 5.3, but even then it's a question whether it's worth it, just for using observers. You can achieve similar things with events and listeners.
Very useful,also I would like to ask, I have a database with this tables. Years, products,sales, Years has many products and sales has many to many relationship with products I want to get data depends on year when I change year ,all products and sales should in that selected Thank you
I can't really write the query for you without running that query locally and trying it out with real data. So if you have this project with data available on Github, please invite me as a collaborator (username PovilasKorop) and I will try to write that query for you.
Not sure what can I elaborate about, it's just one extra sentence, that you can do User::active()->registeredWithinDays(14)->get(); So won't shoot a separate video about it.
Thank you for creating all of this, Povilai. TIkrai ačiū :)
My number one laravel teacher! Thanks you!
Brilliant 👏 👏
very useful, thank you
Brilliant tip. Thank you so much for sharing.
My daily dose of knowledge.
awesome and super explanation
Thank you! Immediately applied in my project.
I think I am going to your fan soon ; )
thank you sir😊
That's reduce the query? On laravel debugbar?
Awesome tips thank you
do you plan to discuss repositort method as well?
You mean repository pattern? I'm not a big fan of it. I explained it in this free lesson of my course "How to structure Laravel project": laraveldaily.teachable.com/courses/how-to-structure-laravel-project/lectures/8760335
@@PovilasKorop oh pattern sorry. thanks!
@@PovilasKorop I appreciate your take on repository patterns. I haven't used it so far in my projects and here I am thinking that it's the "standard" for many companies. thanks!
I freakin love Laravel
Hi Povilas!
I think you should update the Eloquent course to the latest version. Is it viable?
Yes I'm planning to update it in the Autumn, currently updating the testing course, it takes time.
Hei, very helpful and good tip. I have a question about collecting views count. What are the good options for getting page/post views for laravel app and vuejs (only) app? Is this something that would be worth doing video on or mby you can comment on that?
Well, not sure what is problematic here, just in show() method of a controller you do $post->increment('views_count') or something like that.
And if you have Vue app with API, then you should probably have a separate API endpoint to increase views count.
thank you...
how what is difference if you write public function postedWithinDays() without scope inside model?
It won't work, you can try.
does scope work like static function?
@@edigogidze8349 no, scope is a scope, it has separate programmed functionality within Laravel framework.
thank y for your answear ❤
Hey there! Your videos are realyy helpful. Is there any chancee to have your courses in some kind of package? I found 3 of them what really fits my current job of refactoring, so a bundle would be nice. Keep up the good work!
Hi Gergely, I don't have a special package, but I can offer you a deal: if you buy any 2 of my courses, email me povilas@laraveldaily.com and I will assign you another one for free.
@@PovilasKorop Thanks, great! The course "How to Structure..." seems really helpful, and a question pops out already from the preview. I have to deal with an acient project (5.1, all logic in controllers, ~30 models, sad story), after refactoring new funcionality has to be added. However, accessors/mutators introduced, but no model observers in this Laravel version what I miss already.
What is you opinion, to what version would be the lightest 'pain in the ...' to update? 5.3/5.8 or huge refactoring and switch to 8?
@@gram_o_phone From what I remember, the biggest structural change and biggest pain to upgrade was from 5.2 to 5.3, later not much has changed globally in the structure of Laravel project, only new functions added and relatively small changes. So depends on your budget/time, I would advise to upgrade to 5.3, but even then it's a question whether it's worth it, just for using observers. You can achieve similar things with events and listeners.
@@PovilasKorop 👍 for the advice, just enrolled to the course. Based on your videos, your explaining and coding style is really fits to mine. Thanks!
Very useful,also I would like to ask, I have a database with this tables. Years, products,sales,
Years has many products and sales has many to many relationship with products
I want to get data depends on year when I change year ,all products and sales should in that selected
Thank you
I can't really write the query for you without running that query locally and trying it out with real data. So if you have this project with data available on Github, please invite me as a collaborator (username PovilasKorop) and I will try to write that query for you.
thanks
Thanks. Please Elaborate chaining of svopes also
Not sure what can I elaborate about, it's just one extra sentence, that you can do User::active()->registeredWithinDays(14)->get();
So won't shoot a separate video about it.
@@PovilasKorop i was just interested to let others know that chaining does exist in scopes. BTW thanks alot
awesome
Thanks :)
dream to meet and thank you
Eloquent is full shit. Don't use him never in big and mid projects. It is possible to use only for one-page landings or very simple projects.