withStringMatcher asserts the wrong reference

TypedExampleMatcher.withStringMatcher(StringMatcher) validates the wrong reference:

public ExampleMatcher withStringMatcher(StringMatcher defaultStringMatcher) {

    Assert.notNull(ignoredPaths, "DefaultStringMatcher must not be empty");

    return new TypedExampleMatcher(nullHandler, defaultStringMatcher, propertySpecifiers, ignoredPaths,
            defaultIgnoreCase, mode);
}

It asserts the ignoredPaths field instead of the defaultStringMatcher parameter. ignoredPaths is always set, so the assertion always passes, and a null defaultStringMatcher is accepted and stored, only to fail later. The assertion should guard the parameter, as its message already indicates. The sibling method withIgnorePaths(String...) correctly asserts its own parameter.

Start at the TypedExampleMatcher.withStringMatcher(StringMatcher) entry point and compare its validation with the sibling withIgnorePaths(String...) method. Verify that the string matcher parameter, rather than ignoredPaths, is validated, and confirm that null is rejected while valid matchers retain the existing behavior.