DEV Community: Kerry Owston

More info on ambiguous 500 errors

Kerry Owston — Tue, 16 Apr 2024 21:31:39 +0000

While Pest testing in a laravel project I get a 500 HTTP error. Great now what? How can I get more detail from this generic gem?

You can eek out a little more information with this:

$this->withoutExceptionHandling();

Whichh I placed at the top of my test.

It's kind of like:

dd();

But for errors.

Laravel Collections and Resources

Kerry Owston — Tue, 16 Apr 2024 17:47:48 +0000

When working with API's I'd been becoming frustrated with the process around creating resources and collections. Sure when creating resources which seemed to follow a different pattern as when creating migrations, controllers, requests and what not.

Previously when creating contact resource I had used:

a make:resource ContactResource
With a being an alias for PHP artisan.

This was fine for the resource but I also needed a collection.

Intuitively I tried:

a make:collection ContactCollection
Which was the wrong way to go about this.

a make:resource --collection ContactColllection

In the given scenario, Laravel knows that it should create both the resource and its associated collection. This distinction ensures that Laravel sets up the necessary files and configurations for both the resource and its collection correctly.

Users table wiped out after testing.

Kerry Owston — Tue, 16 Apr 2024 12:23:41 +0000

After switching to SQLite and I was wondering why I can't authenticate when trying to log in via Postman.

Since everything was working fine before I started building out my tests this morning.

But suddenly I'm looking at an empty users table where previously there had been several - test users.

The culprit...

phpunit.xml

    <php>
        <env name="APP_ENV" value="testing"/>
        <env name="APP_MAINTENANCE_DRIVER" value="file"/>
        <env name="BCRYPT_ROUNDS" value="4"/>
        <env name="CACHE_STORE" value="array"/>
        <!-- <env name="DB_CONNECTION" value="sqlite"/> -->
        <!-- <env name="DB_DATABASE" value=":memory:"/> -->
        <env name="MAIL_MAILER" value="array"/>
        <env name="PULSE_ENABLED" value="false"/>
        <env name="QUEUE_CONNECTION" value="sync"/>
        <env name="SESSION_DRIVER" value="array"/>
        <env name="TELESCOPE_ENABLED" value="false"/>
    </php>

Simple fix:

Now I no longer experience a wipeout on my db user tables.

Now each test run is on a fresh isolated instance of the database and will not interfere with my project's live data.

2 Great feelings for newbie coders

Kerry Owston — Sun, 12 Nov 2023 19:31:37 +0000

1) The moment you realise that thing you were convinced you will never understand or remember has become second nature - and replaced by some other thing you're convinced you will never understand or remember. 😂

2) When you delay doing some task u gotta do because you're too into the problem you're working on.

Because you are enjoying it.

Which gives you faith you're on the right path.