PSR-4 directory mapping in PHP - Time & Space Complexity

Time Complexity: PSR-4 directory mapping

O(1)

Understanding Time Complexity

Let's see how the time to find a PHP class file grows when using PSR-4 directory mapping.

We want to know how the file lookup time changes as the number of classes grows.

Scenario Under Consideration

Analyze the time complexity of the following PSR-4 autoloader snippet.

function loadClass($className) {
    $prefix = 'App\\';
    $baseDir = __DIR__ . '/src/';

    if (str_starts_with($className, $prefix)) {
        $relativeClass = substr($className, strlen($prefix));
        $file = $baseDir . str_replace('\\', '/', $relativeClass) . '.php';
        if (file_exists($file)) {
            require $file;
        }
    }
}
    

This code maps a class name to a file path and loads it if found.

Identify Repeating Operations

Look for repeated steps when loading classes.

• Primary operation: Checking if the class name starts with the prefix and converting namespace separators to directory separators.
• How many times: Once per class load request.

How Execution Grows With Input

The time to load a class depends on how long it takes to build the file path and check if the file exists.

Input Size (number of classes)	Approx. Operations
10	10 file path builds and checks
100	100 file path builds and checks
1000	1000 file path builds and checks

Pattern observation: Each class load requires a direct path build and file check, so operations grow linearly with the number of classes loaded.

Final Time Complexity

Time Complexity: O(1)

This means loading a single class file takes about the same time regardless of how many classes exist, because the path is computed directly.

Common Mistake

[X] Wrong: "Loading a class gets slower as more classes are added because it searches through all files."

[OK] Correct: PSR-4 uses a direct mapping from class name to file path, so it does not search all files but directly checks one file.

Interview Connect

Understanding how PSR-4 autoloading works and its time complexity shows you know how modern PHP apps efficiently load code on demand.

Self-Check

What if the autoloader had to scan multiple directories for each class? How would the time complexity change?

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