Code here does not match bootcamp.

[morrica]

The code here does not match that in the bootcamp here: https://laravel.com/learn/getting-started-with-laravel

Furthermore, the bootcamp alludes to a ChirpPolicy that is not actually created in the bootcamp and does not appear here, and it apparently relies on that Policy to provide $this->authorize('update', $chirp); functionality in the ChirpController which does not function.

[Languafe]

Under the section "Step 6: Laravel Policies (Preview)" of the "Edit and delete Chirps" lesson, the creation of the Policy class is shown and examples are provided for how the policy can be used for authorization.

I agree this could perhaps have been dropped from this lesson and instead added to the one where authorization is actually implemented, but this is made pretty clear if you read the whole section.

Create the ChirpPolicy class:

php artisan make:policy ChirpPolicy --model=Chirp

And then implement the update and delete methods as follows:

public function update(User $user, Chirp $chirp): bool
{
    return $chirp->user()->is($user);
}

public function delete(User $user, Chirp $chirp): bool
{
    return $chirp->user()->is($user);
}

[jf0772256]

Something that didn't get mentioned was that you have to include and use a trait called AuthorizesRequests for the $this->authorize() to not throw a fit in your controller.

[Languafe]

Something that didn't get mentioned was that you have to include and use a trait called AuthorizesRequests for the $this->authorize() to not throw a fit in your controller.

The last paragraph of the Step 6 section of the Basic authentication: Registration lesson does mention it:

Since we set up that policy to authorize a user to update a particular chirp, we can add that here. This $this->authorize() method will check if they are authorized to update the chirp, then let's continue. We'll need the controller to have the AuthorizesRequests trait that it can use.

[jf0772256]

Ey, it very easy to miss though - I do stand corrected.