Following a little surprise on a Laravel project I was developing, I figured best to write a short post about it. Make sure to be very careful when you use the $with property in your models. Whilst this can be a helpful property – it allows the model to always eager load a relationship or […]
At first I didn’t get PHPSpec’s “inline matchers” but have since discovered how to use them for matching custom conditions in your tests.
It’s amazing how far a few simple examples will take you, and thanks to kind-hearted folk on the net, I’ve had my eyes opened and hopefully can provide some useful examples for other people.
I’ve recently started using PHPSpec to drive my testing efforts in a new Laravel project. The behaviour-driven approach makes a lot of sense to me but I am finding it a little difficult to master.
This post provides a fix if you find PHPSpec throwing Class not found errors after running your test suite on the command line.
I’m building a Laravel 3 application and I wanted to make sure that logged-in users always remain in HTTPS browsing mode no matter what part of the application they are using, whilst visitors can browse around the site in HTTP mode.
Sometimes it’s useful to record when an authorised user was last active in your web application – whether it’s something that you show on the front end to other users, or whether you want to have an admin feature to track possibly inactive users.
There’s a pretty powerful elegance to the Laravel PHP Framework. Here’s an example of just how easy it is to use many-to-many relationships.
In the web app I’m building we allow a “Display Name” so we get users’ full names but give them control. Here’s how to get that info in a Laravel model.
