* </p>
 * <p>
 * The default filter allows common safe classes like primitives, arrays, String,
 * Number types, collections, and classes in the org.codelibs package. For custom
 * requirements, use the overloaded methods that accept a custom filter.
 * </p>
 *
 * @author higa
 */
public abstract class SerializeUtil {

    /**
     * Do not instantiate.
     */
    protected SerializeUtil() {
    }

{* ../../docs_src/query_params_str_validations/tutorial014_an_py310.py hl[10] *}

## Custom Validation { #custom-validation }

There could be cases where you need to do some **custom validation** that can't be done with the parameters shown above.

In those cases, you can use a **custom validator function** that is applied after the normal validation (e.g. after validating that the value is a `str`).

        analyzers.addAnalyzer("custom", customAnalyzerSettings);
    })
    .build();

Suggester customSuggester = Suggester.builder()
    .settings(settings)
    .readingConverter(new ReadingConverterChain())
    .normalizer(new ICUNormalizer())
    .build(client, "custom-suggest");
```

## Configuration Options

### Suggester Settings

```java

 * the symmetry of {@code equals}. Custom definitions of equality are usually based on an interface,
 * such as {@code Set} or {@code List}, so that the implementation of {@code equals} can cast the
 * object being tested for equality to the custom interface. {@code ForwardingObject} implements no
 * such custom interfaces directly; they are implemented only in subclasses. Therefore, forwarding

 * provided by Maven and custom types registered through SPI provider implementations.
 *
 * @since 4.0.0
 */
@Experimental
public interface TypeRegistry extends ExtensibleEnumRegistry<Type> {

    /**
     * Obtain the {@link Type} from the specified {@code id}.
     * If no type is known for {@code id}, the registry will
     * create a custom {@code Type} for it.
     *

    }

    @Test
    public void testBuildWithCustomSettings() {
        // Test building with all custom settings
        String id = "custom-id";
        builder.setSettingsIndexName("CUSTOM_INDEX")
                .addInitialSettings("custom.key1", "value1")
                .addInitialSettings("custom.key2", 42)
                .scrollTimeout("100s")
                .searchTimeout("50s")

Nevertheless, we can declare the expected schema for the request body.

### Custom OpenAPI content type { #custom-openapi-content-type }

Using this same trick, you could use a Pydantic model to define the JSON Schema that is then included in the custom OpenAPI schema section for the *path operation*.

And you could do this even if the data type in the request is not JSON.

# Run tests for specific module
mvn test -pl fess-crawler
```

## Examples

### Web Crawling with Custom Rules

```java
// Create crawler with custom configuration
StandardCrawlerContainer container = new StandardCrawlerContainer();

// Configure HTTP client with custom settings
container.singleton("httpClient", HcHttpClient.class, client -> {
    client.setUserAgent("MyBot/1.0");

But now you know how it works, so you can use relative imports in your own apps no matter how complex they are. 🤓

### Add some custom `tags`, `responses`, and `dependencies` { #add-some-custom-tags-responses-and-dependencies }

We are not adding the prefix `/items` nor the `tags=["items"]` to each *path operation* because we added them to the `APIRouter`.

                                                 title="Floating point number" required="required"
                                                 data-validation="custom"
                                                 data-validation-regexp="(\+|\-)?\d+(\.\d+)?((e|E)(\+|\-)?\d+)?"
                                                 data-validation-help="number (Float)"/>