New video on my Youtube channel Laravel Business - today I want to talk about what to talk about (ironical, right) with the client before the beginning of the project. Usually those conversations save huuuuge amount of time (and potential failures) in process of the project.
Today I've delivered a presentation at my local Laravel Meetup in Vilnius, Lithuania, and now sharing slides with you. Basically, I wanted to research what are available solutions on the market to generate Laravel code automatically instead of writing it manually. Found quite a lot, actually. So now have a bigger picture on various generators and some new ideas for our own QuickAdminPanel generator.
When creating user authorization system with soft-deletable data we might encounter a problem: deleted user might try to register with same email address and gets an error that it is in use. What to do in order to prevent it? Here is a quite simple example of how it could be solved.
Laravel default Auth system is great, but sometimes there's a need that user would register but NOT log in automatically. The problem is that Laravel does auto-login by default after registration. Worry no more, there is a simple solution for that!
Another side-project from my team and me personally. Lately there's quite a lot of books about Laravel, as the framework gets more popular. But the thing I've missed on the market is a non-technical book about Laravel. So here it is - presenting to you "Laravel for Clients"!
We all use Carbon library to manage date and time, right? But who has actually read full documentation of what functions it has? In addition to well-known ones like now() or format(), Carbon has a lot more useful stuff. Let's take a look.
After having launched a couple dozens of projects with Laravel, I decided to create a checklist for the launches. The problem is quite often something is forgotten or overlooked - either from our team side, or from the client. So this checklist should prevent it and possibly would help you in your launches too.
As a tradition of posting little things here on the blog, one more useful detail. What do you do when you need to show a loop in Blade with foreach, but the list might be empty? You probably write if-else statement around it, right?
Lately I've been re-reading full Laravel documentation and found quite a lot of "small details" which no one actually noticed in tutorials or books. One of these is using "-" symbol in route parameters.
