Explore if it makes sense to provide an EvaluationContextExtension supports optional/null query parameters.

Using @Query to skip entire criteria entries when given a null value is cumbersome at the moment but could be done as follows.

interface Repo extends CrudRepository<Person,...> {
  @Query("""
         { $and : [ 
            ?#{T(com.example.Repo.QueryUtil).ifPresent([0], 'name')}, 
            ?#{T(com.example.Repo.QueryUtil).ifPresent([1], 'city')},
            ... 
         ]}
         """)
  List<Person> findByNameAndCity(@Nullable String name, @Nullable String city, ...);

  class QueryUtil {
    public static Document ifPresent(Object value, String property) {
      if(value == null) {
        return new Document("$expr", true); // always true
      }
      return new Document(property, value); // eq match
    }
  }
  // ...
}

Providing an EvaluationContextExtension with predefined methods might help ease a lot of pain.

Start by reviewing the @Query usage and the EvaluationContextExtension mechanism described in the issue. Determine whether predefined methods can support optional or null query parameters, and document the resulting design or implementation scope; the issue names no files or tests.