Bird
0
0

You wrote Route::resource('items', ItemController); but get an error. What is the likely cause?

medium📝 Debug Q6 of 15
Laravel - Routing
You wrote Route::resource('items', ItemController); but get an error. What is the likely cause?
AController class must be a string
BMissing ::class after controller name
CResource name should be singular
DResource routes do not accept controller classes
Step-by-Step Solution
Solution:

  1. Step 1: Check syntax for resource route controller parameter

    The controller must be passed as a class reference using ::class.

  2. Step 2: Identify the error cause

    Omitting ::class causes a syntax or runtime error.

  3. Final Answer:

    Missing ::class after controller name -> Option B

  4. Quick Check:

    Controller must use ::class in resource routes [OK]
Quick Trick: Always add ::class to controller in resource routes [OK]
Common Mistakes:
  • Passing controller as bare class name
  • Using singular resource name incorrectly
  • Assuming string controller name without quotes

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Laravel Quizzes
Configuration and Environment - Logging configuration - Quiz 1easy Configuration and Environment - Why configuration management matters - Quiz 8hard Database Basics and Migrations - Factory definitions - Quiz 12easy Database Basics and Migrations - Database configuration - Quiz 10hard Laravel Basics and Architecture - First Laravel application - Quiz 13medium Laravel Basics and Architecture - Why Laravel exists - Quiz 2easy Request and Response - Query parameters - Quiz 5medium Request and Response - Request validation basics - Quiz 7medium Request and Response - Response types (view, JSON, redirect) - Quiz 3easy Routing - Route prefixes - Quiz 4medium