You need a custom web-project done? We’re here to help. We’re looking at the business goals of the client, and only then turn it into Laravel code.
Laravel is full of little tricks, and quick ways to generate code with Artisan. One of the recent ones I’ve found is when you’re creating a CRUD record and need to create Model + Controller. You don’t need two separate commands for that.
Recently I’ve encountered a situation and want to share a quick solution with you guys. Laravel has quite an awesome feature of Mutators – you can define extra fields in your Eloquent models that are dynamically calculated. But orderBy doesn’t work with them, so what can we do?
On the last episode of Laravel Podcast, Taylor Otwell said something controversial but I had a gut feeling about it for a long time. So, do you actually use down() method in migrations, and rollback them?