Laravel’s routing and binding is nice

But when I got it wrong I didn’t get the kind of error I expected

Laravel automatically resolves Eloquent models defined in routes or controller actions whose type-hinted variable names match a route segment name.

use App\Models\User;
 
Route::get('/users/{user}', function (User $user) {
    return $user->email;
});

Code reviews are a real opportunity to learn from each other - we each write code a little differently and bring with us a range of experience. So much better to spend time on this than debating blank lines.

I’m also slightly dyslexic and find it hard to even see the issues some care passionately about.

I want to do the right thing for the team but going through code line by line and applying a strict set of rules is not something I am good at or enjoy.

Computers are good at following rules though.

I had a docker image and couldn’t find the Dockerfile but wanted to see what was in it

docker image history --no-trunc --format="{{.CreatedBy}}" imagename

How to get code coverage reports from PHPUnit to Sonarqube

I started already having an environment using docker-compose but without xdebug the unit tests couldn’t generate coverage reports.

I wanted to borrow a commit from another branch

git cherry-pick -n some-commit
git reset

A common problem with Laravel seems to be getting 419 errors.

If you have fixed these except for during testing : disable caching.

I love the extra security CSP brings - but it’s still a bit new to me and I hadn’t setup reporting because this is a static site and I didn’t think I had anywhere easy to send the errors.

However I use Sentry for another project and realised that it offers easy CSP reporting.