old_content = content_path.read_text(encoding="utf-8")

    new_content = yaml.dump(new_content, sort_keys=False, width=200, allow_unicode=True)
    if old_content == new_content:
        logging.info(f"The content hasn't changed for {content_path}")
        return False
    content_path.write_text(new_content, encoding="utf-8")
    logging.info(f"Updated {content_path}")
    return True


def main() -> None:

    tester.testStaticMethods(PatternFilenameFilter.class, Visibility.PACKAGE); // currently none

    // The reason that we skip this method is discussed in a comment on the method.
    tester.ignore(PatternFilenameFilter.class.getMethod("accept", File.class, String.class));
    tester.testInstanceMethods(new PatternFilenameFilter(".*"), Visibility.PACKAGE);
  }

Die API-Dokumentation verwendet **Swagger UI** und **ReDoc**, und jede dieser Dokumentationen benötigt einige JavaScript- und CSS-Dateien.

The API docs use **Swagger UI** and **ReDoc**, and each of those need some JavaScript and CSS files.

By default, those files are served from a <abbr title="Content Delivery Network: A service, normally composed of several servers, that provides static files, like JavaScript and CSS. It's commonly used to serve those files from the server closer to the client, improving performance.">CDN</abbr>.

[
	uuid(4fc742e0-4a10-11cf-8273-00aa004ae673),
	version(3.0)
]
interface netdfs
{
	import "../rpc.idl";

	const uint32_t DFS_VOLUME_FLAVOR_STANDALONE = 0x100;
	const uint32_t DFS_VOLUME_FLAVOR_AD_BLOB = 0x200;

	const uint32_t DFS_STORAGE_STATE_OFFLINE = 0x0001;
	const uint32_t DFS_STORAGE_STATE_ONLINE = 0x0002;
	const uint32_t DFS_STORAGE_STATE_ACTIVE = 0x0004;

	typedef struct {
		[string] wchar_t *entry_path;
	} DfsInfo1;

import java.util.HashMap;
import java.util.Map;

import org.codelibs.fess.opensearch.config.allcommon.EsAbstractEntity;
import org.codelibs.fess.opensearch.config.bsentity.dbmeta.BoostDocumentRuleDbm;

/**
 * ${table.comment}
 * @author ESFlute (using FreeGen)
 */
public class BsBoostDocumentRule extends EsAbstractEntity {

    // ===================================================================================

En fait, dans certains cas, il y aura même **deux schémas JSON** dans OpenAPI pour le même modèle Pydantic, pour l'entrée et pour la sortie, selon s'ils ont des **valeurs par défaut**.

Voyons comment cela fonctionne et comment le modifier si vous devez le faire.

## Utiliser des modèles Pydantic pour l'entrée et la sortie { #pydantic-models-for-input-and-output }

    },
    "paths": {
        "/items/": {
            "get": {
                "responses": {
                    "200": {
                        "description": "Successful Response",
                        "content": {
                            "application/json": {



...
```

#### OpenAPI 的用途 { #what-is-openapi-for }

OpenAPI schema 驅動了兩個互動式文件系統。

import org.codelibs.fess.util.ComponentUtil;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.TestInfo;

/**
 * Unit tests for {@link AbstractFessFileTransformer}.
 * Tests file transformation logic including content extraction and metadata handling.
 */
public class AbstractFessFileTransformerTest extends UnitFessTestCase {

    private TestableAbstractFessFileTransformer transformer;

    @Override

/// tip | 豆知識

`aGVsbG8=` は `hello` の base64 エンコードです。

///

その後、Pydantic は base64 文字列をデコードし、モデルの `data` フィールドに元のバイト列を渡します。

次のようなレスポンスを受け取ります:

```json
{
  "description": "Some data",
  "content": "hello"
}
```

## 出力データ向けの Pydantic `bytes` { #pydantic-bytes-for-output-data }

出力データ用にモデル設定で `ser_json_bytes` とともに `bytes` フィールドを使用することもでき、Pydantic は JSON レスポンスを生成するときにバイト列を base64 でシリアライズします。