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

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.

 * 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.
     *

# 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");

/**
 * Form for uploading Kuromoji dictionary files to the Fess search engine.
 * Kuromoji is a Japanese morphological analyzer used for tokenizing Japanese text.
 * This form is used in the admin interface to upload custom user dictionaries for Kuromoji.
 */
public class UploadForm {

    /**
     * The dictionary ID that identifies which Kuromoji dictionary configuration to update.

	return func(network, address string, c syscall.RawConn) error {
		return nil
	}
}

// DialContext is a function to make custom Dial for internode communications
type DialContext func(ctx context.Context, network, address string) (net.Conn, error)

// NewInternodeDialContext configures a custom dialer for internode communications
func NewInternodeDialContext(dialTimeout time.Duration, _ TCPOptions) DialContext {

For example, let's add <a href="https://github.com/Rebilly/ReDoc/blob/master/docs/redoc-vendor-extensions.md#x-logo" class="external-link" target="_blank">ReDoc's OpenAPI extension to include a custom logo</a>.

### Normal **FastAPI** { #normal-fastapi }

First, write all your **FastAPI** application as normally:

{* ../../docs_src/extending_openapi/tutorial001_py39.py hl[1,4,7:9] *}

      }
    },
    "analyzer": {
      "sv_analyzer": {
        "type": "custom",
        "tokenizer": "standard",
        "filter": ["lowercase", "swedish_stop", "swedish_stemmer"]
      }
    }
  }
}
```

### 2. Add Custom Dictionaries (Optional)

Create custom dictionary files in: `${fess.dictionary.path}/[lang]/`

Available dictionary types:

# For most projects, this workflow file will not need changing; you simply need
# to commit it to your repository.
#
# You may wish to alter this file to override the set of languages analyzed,
# or to provide custom queries or build logic.
name: "CodeQL"

on:
  push:
    branches: [master]
  pull_request:
    # The branches below must be a subset of the branches above
    branches: [master]
  schedule:
    - cron: '0 11 * * 4'

jobs:

 * <p>
 * Qualifiers are used to distinguish between multiple beans of the same type,
 * allowing for more precise control over which implementation should be injected.
 * Custom qualifier annotations should be annotated with {@code @Qualifier}.
 * <p>
 * Example of creating a custom qualifier:
 * <pre>
 * {@literal @}Qualifier
 * {@literal @}Retention(RUNTIME)
 * public @interface Database {
 *     String value();
 * }
 * </pre>
 *