如何避免在方法链式调用中进行空值检查？

Absolutely, dealing with those endless chained != null checks is such a tedious chore—no one wants to write or maintain that messy boilerplate. Here are several practical, clean ways to avoid manually verifying every nested method call:

1. Use Java 8+ Optional (Most Standard Approach) #

Optional was built specifically to handle nullable values gracefully. Wrap your root object, chain map() calls to traverse the nested structure, then check if the final value exists:

isValid = Optional.ofNullable(country)
    .map(Country::getCity)
    .map(City::getSchool)
    .map(School::getStudent)
    // Add more map() calls for deeper nesting as needed
    .isPresent();

Each map() safely skips null values—if any step returns null, the rest of the chain short-circuits, and isPresent() returns false. This fits exactly your use case where you only need to confirm the entire chain is non-null.

2. Safe Navigation Operator (JVM Languages Like Groovy/Kotlin) #

If your tech stack allows it, the safe navigation operator (?.) is a game-changer. It automatically stops evaluating the chain the moment it hits a null:

Groovy Example: #

isValid = country?.city?.school?.student != null

Kotlin Example: #

isValid = country?.city?.school?.student != null

This is by far the most concise option available for JVM languages that support it.

3. Utility Method with Try-Catch (For Pre-Java 8) #

If you’re stuck on an older Java version, create a simple utility method that uses exception handling to catch null pointer exceptions implicitly:

import java.util.function.Supplier;

public class NullCheckUtils {
    public static <T> boolean isChainNonNull(Supplier<T> supplier) {
        try {
            return supplier.get() != null;
        } catch (NullPointerException e) {
            return false;
        }
    }
}

Call it like this:

isValid = NullCheckUtils.isChainNonNull(() -> country.getCity().getSchool().getStudent());

The lambda lets you write the nested call naturally, and the try-catch handles any nulls along the way. Just note that some teams might have reservations about catching NullPointerException, so align with your team’s conventions first.

4. Project Lombok (Preventative Measure) #

While not a direct fix for existing nested checks, Lombok’s @NonNull and @NonNullApi annotations can help prevent nulls from propagating in the first place. Adding @NonNull to method parameters or fields generates automatic null checks at compile time, reducing the need for these chained checks later.

内容的提问来源于stack exchange，提问作者user9521067