Create one time click urls

Here is an AI generated answer, so you can get inspired, seems pretty ok to me:

To achieve this, you can introduce a new table (let's call it request_actions) in your database to keep track of whether a request has been acted upon or not. This table can have fields like user_id, accountant_id and status.

When a request is made, an entry is created in this table with the status as 'pending'. When either the 'accept' or 'reject' action is performed, the status is updated to 'used'.

Before performing any action, you can check the status of the request. If it's 'used', you can prevent the action and return a message to the user.

Here is how you can modify your acceptRequest method:

public function acceptRequest($userId, $accountantId)
{
    $requestAction = RequestAction::where('user_id', $userId)
                                  ->where('accountant_id', $accountantId)
                                  ->first();

    if ($requestAction && $requestAction->status == 'used') {
        return redirect('/')->with('error_message', 'This request has already been acted upon.');
    }

    $accountant = User::findOrFail($accountantId);
    $user = User::findOrFail($userId);

    $accountant->users()->attach($userId);

    // Update the request action status to 'used'
    if ($requestAction) {
        $requestAction->status = 'used';
        $requestAction->save();
    }

    $data = [
        'email' => '[email protected]',
        'name' => 'test name',
        'accountantName' => $accountant->name,
        'userName' => $user->name,
    ];

    Mail::to($accountant->email)->send(new Email($data, 'accept-accountant-request'));
    return redirect('/')->with('success_message', 'Success');
}

You would need to do a similar check in your rejectRequest method as well.

Please note that you would need to create a new model RequestAction and a migration for the request_actions table. Also, don't forget to create an entry in the request_actions table when a new request is made.

@tsitsi98 I have no idea what it is that is being “accepted” or “rejected” as your route and controller naming is a mess. Try to follow resourceful resource naming when creating your routes.

In an answer to the actual question, if you’re “accepting” or “rejecting” something then all you need to do is check if whatever model has already been accepted or rejected. If it has, return an error response. If not, accept/reject it.

class FooController extends Controller
{
    public function accept(Foo $foo)
    {
        abort_if($foo->hasBeenAccepted() || $foo->hasBeenRejected(), 400);

        $foo->accept();

        return redirect()->to('/somewhere');
    }

    public function reject(Foo $foo)
    {
        abort_if($foo->hasBeenAccepted() || $foo->hasBeenRejected(), 400);

        $foo->reject();

        return redirect()->to('/somewhere');
    }
}

So above, it’s clear to see that it’s a Foo model that a user can accept or reject. The corresponding URLs would look something like /foos/{foo}/accept and /foos/{foo}/reject (with the signature appended of course).