{"id":9808,"date":"2021-04-09T10:00:12","date_gmt":"2021-04-09T01:00:12","guid":{"rendered":"https:\/\/www.gigas-jp.com\/appnews\/?p=9808"},"modified":"2021-04-08T19:09:17","modified_gmt":"2021-04-08T10:09:17","slug":"prohibited-validation-rules-in-laravel","status":"publish","type":"post","link":"https:\/\/www.gigas-jp.com\/appnews\/archives\/9808","title":{"rendered":"Prohibited Validation Rules in Laravel"},"content":{"rendered":"\n

Sometimes we wish to forcefully prevent some of the fields in the request. <\/p>\n\n\n\n

Now we just got that. Laravel 8 has three validation added for prohibited fields. Let\u2019s walk through a few examples of where the prohibited validation rules might be useful and look at each one in more detail.<\/p>\n\n\n\n

Prohibited Validation Rule<\/strong><\/p>\n\n\n\n

The \u201cprohibited<\/strong>\u201d rule checks if the field under validation must be empty or not present or throw an error otherwise.<\/p>\n\n\n\n

\/\/ PUT \/api\/licenses\/123-456\n\n\/\/ {\"name\":\"hello-world\", \"key\":\"random-key\"}\n\n$validated = $request->validate([\n    'name' => 'required|max:255',\n    'key' => 'prohibited',\n]);\n\t\t\t\n\/\/ Response: 422\n\n\/\/ The key field is prohibited\n<\/code><\/pre>\n\n\n\n
The above is where a user might expect to update an API key by sending a PUT request to a resource. That field is likely ignored during the request. However, a successful response might lead to the user to believe they were able to update the key <\/strong>when in reality, the API ignored it. <\/p>\n\n\n\n
If  prohibited validation rule registers, the key <\/strong>field is present in the request it will terminate the request with 422 HTTP code response code  and throw the error with the message The key field is prohibited.<\/strong><\/p>\n\n\n\n
Prohibited If and Unless Rules<\/strong><\/p>\n\n\n\n
The  \u201cprohibited_if \u201d <\/strong> rule checks if the field under validation must be empty or not present if the another field is equal to any value.<\/p>\n\n\n\n
Validator::validate([\n\u2018is_minor\u2019 => true,\n\u2018tos_accepted\u2019 => true\n], [\n\u2018tos_accepted\u2019 => \u2018prohibited_if:is_minor, true\u2019\n]);<\/code><\/pre>\n\n\n\n
The above example is we\u2019re expecting tos_accepted field will be forbidden if is_minor filed accepts true value. This example means someone accepting terms of service that has identified as a minor. Perhaps the application requires a parental registration to consent on their behalf.<\/p>\n\n\n\n
The basic idea of  \u201cProhibited_unless\u201d<\/strong> rule is that a given filed should be prohibited from having data unless another field is equal to any value.<\/p>\n\n\n\n
Validator::validate([\n\u2018is_deceased\u2019 => false,\n\u2018date_of_death\u2019 => \u20182021-03-09\u2019\n], [\n\u2018date_of_death\u2019 => \u2018prohibited_unless:is_deceased,true\u2019\n]);<\/code><\/pre>\n\n\n\n
The above example might be initially the is_deceased filed set to false value.If we\u2019re expecting the date_of_death field not to be forbidden, the is_deceased\u2019 field set to true value.The example  illustrates perfectly how to use this rule to explicitly<\/em> prevent contradictory input.<\/p>\n\n\n\n
By Ami<\/p>\n
\n            
<\/g:plusone><\/div>\n            
 \"\u3053\u306e\u30a8\u30f3\u30c8\u30ea\u30fc\u3092\u306f\u3066\u306a\u30d6\u30c3\u30af\u30de\u30fc\u30af\u306b\u8ffd\u52a0\"<\/a>