I’ve recently found out about a feature in Laravel relationship which changed the way I write code. So sharing with you.
A few days ago I started a survey about the tools that Laravel people use. I’ve spread the word on Twitter, and asked some people via Direct Messages, so got 52 responses. Here are the answers to 5 questions I asked.
Resource controllers are great for CRUDs, but if we use them for APIs, there are two unnecessary methods – create() and edit(), cause there are no visual forms for it. So how to remove them from routes? There are two ways.
Resource controllers are amazing tool to work with CRUD functions in Laravel. But what if their default functionality isn’t 100% suitable and you want to override some defaults? Let’s see what you can do.
A quick tip for the case if you need to add additional GET parameters to your route URL, but don’t want to specify them in Routes file. Apparently, there’s a simple way.
Recently I became much more interested in automated testing – PHPUnit, TDD, Laravel Dusk, Travis and other keywords became “closer”,
A short list in “Did you know…?” style. Laravel has a convenient validation mechanism, but most of us only use simple rules like ‘required’, ’email’ or ‘date’. Actually, there are a few less-known but pretty interesting ones. Let’s have a look.
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?