PSR-4 directory mapping in PHP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is PSR-4 in PHP?

PSR-4 is a standard for autoloading PHP classes from file paths that match their namespaces. It helps PHP find and load classes automatically based on their namespace and class name.

beginner

How does PSR-4 map namespaces to directories?

PSR-4 maps a namespace prefix to a base directory. The namespace parts after the prefix become subdirectories inside that base directory, and the class name becomes the file name with a .php extension.

beginner

Example: If the namespace prefix is App\ mapped to src/, where is the class App\Controllers\HomeController located?

The class App\Controllers\HomeController is located at src/Controllers/HomeController.php.

intermediate

Why is PSR-4 preferred over older autoloading methods?

PSR-4 is preferred because it is simple, standardized, and avoids conflicts. It makes code easier to organize and share by following a clear rule to find classes based on namespaces.

intermediate

What happens if a class file does not follow PSR-4 directory mapping?

If a class file does not follow PSR-4 mapping, the autoloader will not find the file automatically, causing errors like "class not found". You must then load the file manually or fix the directory structure.

What does PSR-4 autoloading map to find a class file?

A Function name to URL path

B Class name to database table

C Namespace prefix to base directory

D Variable name to environment variable

PSR-4 maps a namespace prefix to a base directory to locate class files.

If the namespace is MyApp\Models\User and prefix MyApp\ maps to lib/, where is the class file?

A lib/User.php

B lib/MyApp/Models/User.php

C Models/User.php

D lib/Models/User.php

The namespace after prefix becomes subdirectories: Models/User.php inside lib/.

What file extension does PSR-4 expect for class files?

A .php

B .txt

C .inc

D .class

PSR-4 expects PHP class files to have the .php extension.

What error occurs if PSR-4 mapping is incorrect?

A Class not found error

B Syntax error

C Memory overflow

D Division by zero

Incorrect mapping causes "class not found" errors because the autoloader can't find the file.

Which of these is NOT a benefit of PSR-4?

A Standardized autoloading

B Automatically compiles PHP to machine code

C Simplifies class loading

D Avoids naming conflicts

PSR-4 does not compile PHP to machine code; it only standardizes autoloading.

Explain how PSR-4 directory mapping works in PHP autoloading.

Think about how namespaces relate to folder paths.

Describe a common error when PSR-4 directory mapping is not followed and how to fix it.

Consider what happens if the autoloader can't find the file.

Practice

1. What is the main purpose of PSR-4 in PHP?
PSR-4 helps with:

easy

A. Mapping namespaces to directory paths for autoloading classes

B. Defining coding style rules for PHP files

C. Encrypting PHP source code for security

D. Managing database connections automatically

Solution

1. Step 1: Understand PSR-4 role

   PSR-4 is a standard that maps PHP namespaces to folder paths to load classes automatically.

2. Step 2: Compare options

   Only Mapping namespaces to directory paths for autoloading classes describes this mapping and autoloading purpose correctly.

3. Final Answer:

   Mapping namespaces to directory paths for autoloading classes -> Option A

4. Quick Check:

   PSR-4 = Namespace to folder mapping [OK]

Hint: PSR-4 links namespaces to folders for autoloading [OK]

Common Mistakes:

• Confusing PSR-4 with coding style rules
• Thinking PSR-4 encrypts code
• Assuming PSR-4 manages databases

2. Which of the following is the correct way to define a PSR-4 autoload entry in composer.json?

easy

A. "autoload": { "psr-4": { "App": "src" } }

B. "autoload": { "psr-4": { "App/": "src\\" } }

C. "autoload": { "psr-4": { "App\\": "src/" } }

D. "autoload": { "psr-4": { "App\\": "src\\" } }

Solution

1. Step 1: Check PSR-4 syntax in composer.json

   PSR-4 keys use double backslashes for namespace separator and forward slashes for folder paths.

2. Step 2: Validate each option

   "autoload": { "psr-4": { "App\\": "src/" } } correctly uses "App\\" for namespace and "src/" for directory path.

3. Final Answer:

   "autoload": { "psr-4": { "App\\": "src/" } } -> Option C

4. Quick Check:

   Namespace ends with \\ and folder path uses / [OK]

Hint: Use double backslashes for namespaces, forward slashes for folders [OK]

Common Mistakes:

• Using single backslash in JSON string
• Mixing slashes in folder paths
• Omitting trailing backslash in namespace

3. Given this composer.json snippet:

{
  "autoload": {
    "psr-4": {
      "MyApp\\": "app/"
    }
  }
}

Where should the class MyApp\Controllers\HomeController be located?

medium

A. app/Controllers/HomeController.class.php

B. app/MyApp/Controllers/HomeController.php

C. src/Controllers/HomeController.php

D. app/Controllers/HomeController.php

Solution

1. Step 1: Understand PSR-4 mapping

   The namespace prefix "MyApp\\" maps to folder "app/". The rest of the namespace after prefix maps to subfolders.

2. Step 2: Map class namespace to file path

   Class "MyApp\\Controllers\\HomeController" maps to "app/Controllers/HomeController.php".

3. Final Answer:

   app/Controllers/HomeController.php -> Option D

4. Quick Check:

   Namespace after prefix = Controllers/HomeController.php [OK]

Hint: Namespace after prefix = folder path + class name.php [OK]

Common Mistakes:

• Adding namespace prefix folder again
• Using wrong base folder like src/
• Wrong file extension

4. You have this composer.json autoload section:

{
  "autoload": {
    "psr-4": {
      "Lib\\": "lib/"
    }
  }
}

But when you try to use Lib\Utils\Helper, PHP cannot find the class. What is the likely problem?

medium

A. Composer dump-autoload was not run after adding the class

B. The class file is not located at lib/Utils/Helper.php

C. The namespace prefix "Lib\\" should not have trailing backslash

D. The folder path should be "lib\\" with double backslashes

Solution

1. Step 1: Check common PSR-4 issues

   Folder path uses forward slashes, trailing backslash in namespace prefix is correct, so options C and D are wrong.

2. Step 2: Verify autoload update

   After adding new classes, you must run composer dump-autoload to update the autoloader.

3. Final Answer:

   Composer dump-autoload was not run after adding the class -> Option A

4. Quick Check:

   Run dump-autoload after changes [OK]

Hint: Always run composer dump-autoload after adding classes [OK]

Common Mistakes:

• Changing folder slashes incorrectly
• Removing trailing backslash in namespace prefix
• Forgetting to update autoloader

5. You want to autoload two separate namespaces in your project:
"App\\": "src/", "Vendor\\Package\\": "vendor/package/src/"
Which composer.json snippet correctly sets this up?

hard

A. "autoload": { "psr-4": { "App/": "src/", "Vendor/Package/": "vendor/package/src/" } }

B. "autoload": { "psr-4": { "App\\": "src/", "Vendor\\Package\\": "vendor/package/src/" } }

C. "autoload": { "psr-4": { "App\\": "src/", "Vendor\\Package": "vendor/package/src" } }

D. "autoload": { "psr-4": { "App": "src", "Vendor\\Package\\": "vendor/package/src/" } }

Solution

1. Step 1: Check namespace keys format

   Namespace keys must end with double backslashes to separate namespaces properly.

2. Step 2: Check folder paths format

   Folder paths use forward slashes and end with a slash for directories.

3. Step 3: Validate each option

   "autoload": { "psr-4": { "App\\": "src/", "Vendor\\Package\\": "vendor/package/src/" } } correctly uses double backslashes for both namespaces and trailing slashes for folders.

4. Final Answer:

   "autoload": { "psr-4": { "App\\": "src/", "Vendor\\Package\\": "vendor/package/src/" } } -> Option B

5. Quick Check:

   Double backslashes + trailing slash folder paths [OK]

Hint: Use double backslashes for namespaces and trailing slash for folders [OK]

Common Mistakes:

• Omitting trailing backslash in namespace keys
• Using forward slashes in namespace keys
• Missing trailing slash in folder paths