Yeah. I was thinking the same. I just called this "unlike" and will destroy the relation or delete the Like entity.

In the Likeable trait I added this method to remove the Like entity:

public function unlike(?User $user = null)
{
    $this->likes->where('user_id', $user->id ?? auth()->id())->first()->delete();
}

I'm not using the DELETE route to set the dislike. Instead I'm using this four routes:

Route::post('/tweet/{tweet}/like', 'TweetLikesController@storeLike')->name('tweet.like');
Route::post('/tweet/{tweet}/dislike', 'TweetLikesController@storeDislike')->name('tweet.dislike');
Route::delete('/tweet/{tweet}/like', 'TweetLikesController@destroyLike');
Route::delete('/tweet/{tweet}/dislike', 'TweetLikesController@destroyLike');

The corresponding code in the TweetLikesController should be self explanatory. In the view I use this snipped to switch the method to delete, when the user already liked or dislike the tweet:

@if($tweet->isLikedBy(auth()->user()))
    @method('delete')
@endif

The two DELETE routes are somewhat redundant. But like so it's easier in the view.

Build a Like/Dislike System

Updated Series Available