Inconsistencies in how boolean request fields are handled

[navaneeth-raman-bhaskar]

GET

When using the GET request, Boolean validation can fail because form inputs from a GET request are often treated as strings, and Laravel's built-in boolean validation rule is strict, accepting only true, false, "1", "0", 1, and 0.

The following will fail for the URL https://your-dns/api/users?active=true

public function rules(): array
{
    return [
        'active' => ['sometimes', 'required', 'boolean'],
    ];
}

POST

The Boolean validation rule only allows true, false, 1, 0, "1", and "0" values. It doesn't handle strings like 'yes', 'no', 'on', or 'off' by default. However, $request->boolean('active') can transform those values into boolean true or false.

Laravel's request validation Declined validates "no", "off", 0, "0", false, or "false" while Accepted validates "yes", "on", 1, "1", true, or "true". However, there is no built-in accepted_or_declined rule to handle both at once.