Vue.js is getting more and more popular, and good thing about it that it’s pretty quick to get started with. Let me show you an example in this tutorial and sample project.
Laravel pagination is quite a simple thing to use, but to determine the amount of pages it makes additional query to the database, which may be a problem for bigger amount of data. And you can actually avoid it.
Imagine a situation that you have 10 records to show in Blade but you need to show them in 2 sections, five records each. There’s a pretty nice trick how to do that in @foreach loop.
While seeding data, it’s common to have one class for each database table. But what if there are relationships? I
This post is inspired by some discussions that appear constantly in various forums or social media channels. Question of the day/month/year: why is there no app/Models folder? And do we need one?
For a while many of us used to write conditional queries with “if-else”. What if I told you there’s a (much) better way? Easily readable and more Laravel-ish.
While working internally with Laravel APIs and Vue.js, decided to create a sample open-source project to show how it all works together.
In some systems it is required to change password every X days: in banking sector, or working with more sensitive data. Laravel doesn’t have that functionality out-of-the-box, but it’s easy to build. Let’s do it today.
Let’s imagine a scenario where you have an old database and re-writing codebase to Laravel. Database structure may not follow Laravel standards – created_at and updated_at fields are named differently. How can you “tell it to Laravel”?