A Web Developer’s Blog
This is a silly one.
I wanted to run Laravel in dev mode but using the compiled js and scss from npm run build via vitejs.
This usually works
but for some reason Laravel was trying to serve js/css from http://localhost:5173/@vite/client
a service I usually run - but I wanted to test the build stuff.
The solution is really simple but not well documented.
Laravel Validation supports rules forcing unique values - but exceptions are usually needed.
For example if you have articles on a site where each has a slug that has to be unique - when you update the article it has to possible to save the article using the slug it already has.
https://laravel.com/docs/10.x/validation#rule-unique
I have a Laravel project using vite InertiaJS and React
A unit test calling the Head module from @inertiajs/react
Was triggering this error
Cannot read properties of undefined (reading 'createProvider')
For this test I don’t really care about the Head module - but didn’t want to try and mock the whole of inertia-react
Read more ...For some reason I always seem to struggle getting code coverage reports picked up by SonarQube - the documentation isn’t bad but it seems to take me a while to find the right incantation .
I wanted both my PhpUnit tests and Javascript unit tests for my laravel project to generate coverage reports and import this to SonarQube.
Read more ...
The Laravel Docs have a section Constraining Eager Loads
Which hides a lot of power available to you while loading relationships.
It can be used for more than just “constraints”
If you want to sort your relations by a specific fields, add a count of a nested relationship, or in other ways add to teh query - this is where you can do it.
I am working on a project that makes use React within Laravel.
I didn’t find much support for setting up React tests.
So here are som notes on how I got it working.
I needed to send password reset emails from Laravel with additional data so that depending on how the password reset is triggered the email content varies.
You may not need this, if you can manage multiple types of user via roles and permissions it will be much the simpler route to follow.
In my case I wanted user with different: properties, relationships, routes, password rules, timeouts, and more.
It was worth the pain of setting up two authenticatable models.
Laravel is very flexible and well documented, but the further you stray from what most people do - the less obvious it is and a few of these steps took me a while to figure out.
Read more ...
I am working on an application that needs to be able to login to a Laravel instance via API.
In my usual workflow all the session management and XSRF protection has been automagical but I needed to be able to build a test case - and all the docs seemed to assume it would “Just Work™”
Read more ...I’m a long time Linux user, and a big fan of Docker, Kubernetes, VMs, and containers.
While I love developing on Linux - I do sometimes find it frustrating that I don’t have the same level of access to the Microsoft suite on Linux.
A while ago I had to use a Windows laptop for a few days and tried out using WSL - so most of the time I’m in Linux - I didn’t entirely hate it so when it was time for an upgrade I decided to try the Windows route this time.
I’ve had my new machine for a little over a week now.