Custom error messages in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when a validation fails with a custom error message in Laravel?

Consider this Laravel validation snippet inside a controller method:

request()->validate(["email" => "required|email"], ["email.required" => "Email is mandatory."])

What error message will the user see if the email field is left empty?

A The custom message: "Email is mandatory."

B No error message will be shown.

C The default message: "The email field is required."

D A system error will occur due to missing message.

💡 Hint

Custom messages override default messages for specific rules.

Laravel uses the custom message provided for the 'email.required' rule instead of the default one.

📝 Syntax

intermediate

Which option correctly defines a custom error message for the 'min' rule on a 'password' field?

You want to show the message "Password must be at least 8 characters." when the password is too short. Which code snippet correctly sets this in Laravel validation?

A ['min.password' => 'Password must be at least 8 characters.']

B ['password_min' => 'Password must be at least 8 characters.']

C ['password.min' => 'Password must be at least 8 characters.']

D ['password: min' => 'Password must be at least 8 characters.']

💡 Hint

The format is 'field.rule' as the key.

Laravel expects custom messages keys in the format 'field.rule'. Only option C follows this.

🔧 Debug

advanced

Why does this custom error message not show up?

Given this validation code:

request()->validate([
  'username' => 'required|alpha'
], [
  'username.alpha' => 'Username must only contain letters.'
]);

If the username contains numbers, what happens and why might the custom message not appear?

A A syntax error occurs due to missing commas.

B The default message shows because the rule name is misspelled in the custom messages.

C No validation error occurs because 'alpha' allows numbers.

D The custom message shows correctly as expected.

💡 Hint

Check the rule name spelling and message key format.

The 'alpha' rule disallows numbers, and the custom message key matches the rule, so the custom message appears.

❓ state_output

advanced

What is the output of this validation with multiple custom messages?

Consider this validation snippet:

request()->validate([
  'age' => 'required|integer|min:18'
], [
  'age.required' => 'Age is required.',
  'age.min' => 'You must be at least 18 years old.'
]);

If the age field is submitted as 16, what error message will be shown?

A No error message will show.

B "You must be at least 18 years old."

C Both messages will show together.

D "Age is required."

💡 Hint

Only the rules that fail trigger messages.

Since age is provided but less than 18, only the 'min' rule fails and its custom message shows.

🧠 Conceptual

expert

How does Laravel prioritize custom error messages when both attribute and rule messages exist?

You define these messages:

[
  'email.required' => 'Email is required.',
  'required' => 'This field is required.'
]

When the email field is empty, which message will Laravel show and why?

A It shows 'Email is required.' because field-specific messages override general ones.

B It shows 'This field is required.' because general messages override field-specific ones.

C It shows both messages concatenated.

D It shows the default Laravel message ignoring custom ones.

💡 Hint

Laravel uses the most specific message available.

Laravel prioritizes messages for specific fields and rules over general rule messages.