Why Null safe operator in PHP? - Purpose & Use Cases

The Big Idea

What if you could avoid endless checks and crashes when data is missing, with just one simple symbol?

The Scenario

Imagine you have a list of friends, and you want to check their phone numbers. But some friends might not have a phone number saved. You try to look up the number manually by checking each friend one by one.

The Problem

Manually checking each friend's phone number means writing many if-statements to see if the friend exists, then if the phone number exists. This is slow, messy, and easy to forget, causing errors or crashes when a phone number is missing.

The Solution

The null safe operator lets you check for missing values in a simple, clean way. It automatically stops and returns null if something is missing, so your code stays short and safe without many checks.

Before vs After

✗ Before

$phone = null;
if ($friend !== null) {
  if ($friend->contact !== null) {
    $phone = $friend->contact->phone;
  }
}

✓ After

$phone = $friend?->contact?->phone;

What It Enables

It enables writing clear and safe code that gracefully handles missing data without crashes or long checks.

Real Life Example

When building a social app, you can safely get a user's profile picture URL even if the user or picture is missing, avoiding errors and showing a default image instead.

Key Takeaways

Manual checks for missing data are slow and error-prone.

The null safe operator simplifies these checks into one clean expression.

This makes your code safer, shorter, and easier to read.

Practice

1. What does the null safe operator ?-> do in PHP?

easy

A. It allows accessing a property or method only if the object is not null, otherwise returns null.

B. It throws an error if the object is null when accessing a property or method.

C. It converts null values to empty strings automatically.

D. It forces the object to be non-null before accessing properties or methods.

Solution

1. Step 1: Understand the null safe operator purpose

   The null safe operator ?-> is used to safely access properties or methods of an object that might be null.

2. Step 2: Behavior when object is null

   If the object is null, instead of throwing an error, it returns null immediately without calling the property or method.

3. Final Answer:

   It allows accessing a property or method only if the object is not null, otherwise returns null. -> Option A

4. Quick Check:

   Null safe operator = safe access or null return [OK]

Hint: Think: safe access without errors returns null if null [OK]

Common Mistakes:

• Assuming it throws an error on null
• Confusing it with the regular object operator ->
• Thinking it converts null to empty string

2. Which of the following is the correct syntax to use the null safe operator in PHP?

easy

A. $user.?getName();

B. $user->?getName();

C. $user?->getName();

D. $user?getName();

Solution

1. Step 1: Recall the correct null safe operator syntax

   The null safe operator is written as ?-> immediately after the variable name.

2. Step 2: Check each option

   $user?->getName(); uses ?-> correctly. Options B, C, and D have incorrect placements or missing characters.

3. Final Answer:

   $user?->getName(); -> Option C

4. Quick Check:

   Correct syntax = ?-> [OK]

Hint: Remember: question mark before arrow ?-> is correct [OK]

Common Mistakes:

• Placing ? after -> or in wrong position
• Using only ? without ->
• Confusing with ternary operator syntax

3. What will be the output of the following PHP code?

$user = null;
echo $user?->getName() ?? 'Guest';

medium

A. Empty string

B. Error: Call to a member function getName() on null

C. null

D. Guest

Solution

1. Step 1: Evaluate the null safe operator usage

   $user is null, so $user?->getName() returns null safely without error.

2. Step 2: Apply null coalescing operator

   The expression uses ?? 'Guest', so since left side is null, it returns 'Guest'.

3. Final Answer:

   Guest -> Option D

4. Quick Check:

   Null safe + null coalescing = fallback value [OK]

Hint: Null safe returns null, ?? provides fallback [OK]

Common Mistakes:

• Expecting an error when calling method on null
• Confusing null safe with regular -> operator
• Ignoring the null coalescing fallback

4. Identify the error in the following PHP code using the null safe operator:

$order = null;
echo $order?->getItem()->getName();

medium

A. No error, code runs fine and outputs null.

B. Error because getItem() is called on null without null safe operator.

C. Syntax error due to missing semicolon.

D. Error because null safe operator cannot be chained.

Solution

1. Step 1: Analyze the null safe operator chaining

   The first null safe operator ?-> safely calls getItem() on $order which is null, so it returns null.

2. Step 2: Check the next method call

   Then getName() is called on the result of getItem() without null safe operator, causing an error because it's called on null.

3. Final Answer:

   Error because getItem() is called on null without null safe operator. -> Option B

4. Quick Check:

   Chained calls need ?-> on each nullable step [OK]

Hint: Use ?-> before every nullable method call in chain [OK]

Common Mistakes:

• Assuming one ?-> covers all chained calls
• Ignoring that getName() is called on null
• Thinking null safe operator fixes all errors automatically

5. Given the following PHP code, what will be the output?

class Profile {
    public ?string $nickname = null;
}

class User {
    public ?Profile $profile = null;
}

$user = new User();
$user->profile = new Profile();
$user->profile->nickname = null;

echo $user?->profile?->nickname ?? 'No nickname';

hard

A. No nickname

B. null

C. Error: Cannot access property on null

D. Empty string

Solution

1. Step 1: Trace object properties and null safe operator

   $user is an object, $user->profile is an object, but $user->profile->nickname is null.

2. Step 2: Evaluate null safe operator and null coalescing

   The expression $user?->profile?->nickname safely returns null because nickname is null. Then ?? 'No nickname' returns 'No nickname'.

3. Final Answer:

   No nickname -> Option A

4. Quick Check:

   Null safe returns null, ?? fallback used [OK]

Hint: Null safe returns null, ?? gives fallback string [OK]

Common Mistakes:

• Expecting null output instead of fallback string
• Thinking null safe operator throws error on null property
• Confusing null and empty string values