Make Bookings and View/Cancel Them

I think we need used query in (Show) method

$booking = Booking::where('id', $booking)->withTrashed()->first();

Not 100% sure actually, but in the repository that test didn't fail. Could you compare to the repository, please?

Yes I compare to repository, still (test_user_can_cancel_their_booking_but_still_view_it) fail.

In these lines assert status 200 but in my test return 404, so the test fail

$response = $this->actingAs($user1)->getJson('/api/user/bookings/' . $booking->id); $response->assertStatus(200);

Just cloned the last version of the repo, and that test passes for me: ✓ user can cancel their booking but still view it

That said, found that another test is failing after my last new lesson, so thanks for reminding me to rerun php artisan test, need to update another lesson :)

Thanks for you, This course is the most course I found it for me, It contains more than learning how to build project.

Any fix for this ?

Yes, I organized the messages in json format like this. app/Exception/Handler.php

use Symfony\Component\HttpKernel\Exception\NotFoundHttpException;
use Illuminate\Http\Request;

   public function register()
    {
        $this->renderable(function (NotFoundHttpException $e, Request $request) {
            if ($request->is('api/*')) {
                return response()->json([
                    'message' => $e->getMessage()
                ], 404);
            }
        });
    }

It's hard to debug the error for you, as I didn't encounter that error myself. For some reason, the start_date is empty in your case, how can it be null, maybe you're not passing it? Every booking needs to have a start_date. Or maybe you haven't defined it in the Factory? Please check your code and compare to the original repository.

test_user_can_cancel_their_booking_but_still_view_it fails for me, it doesn't find cancelled (softDeleted) booking. It's strange because in Postman they do work!!

@Luis can't really comment or debug without seeing the full code, sorry

Thank you for spotting this - indeed it should have been in the API file!