}
```

/// tip

`aGVsbG8=` 是 `hello` 的 base64 編碼。

///

接著 Pydantic 會將該 base64 字串解碼，並在模型的 `data` 欄位中提供原始位元組。

你會收到類似以下的回應：

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

## Pydantic `bytes` 用於輸出資料 { #pydantic-bytes-for-output-data }

你也可以在模型設定中搭配 `ser_json_bytes` 使用 `bytes` 欄位來處理輸出資料；當產生 JSON 回應時，Pydantic 會將位元組以 base64 進行序列化。

```

/// 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로 “직렬화”합니다.

    * `200`, varsayılan status code'dur ve her şeyin "OK" olduğunu ifade eder.
    * Başka bir örnek `201` ("Created") olabilir. Genellikle veritabanında yeni bir kayıt oluşturduktan sonra kullanılır.
    * Özel bir durum ise `204` ("No Content")'tür. Client'a döndürülecek içerik olmadığında kullanılır; bu nedenle response body olmamalıdır.

That will merge the `.md` files in `next` into a single file.
Atomically (as close to it as possible) add that file to `_content/doc` directory
of the website repository and remove the `doc/next` directory in this repository.

To begin the next release development cycle, populate the contents of `next`
with those of `initial`. From the repo root:

    > cd doc
    > cp -R initial/ next

Dies ist ein Codeschnipsel: `foo`. Und dies ist ein weiteres Codeschnipsel: `bar`. Und noch eins: `baz quux`.

////

//// tab | Info

Der Inhalt von Codeschnipseln sollte unverändert bleiben.

Siehe Abschnitt `### Content of code snippets` im allgemeinen Prompt in `scripts/translate.py`.

////

## Anführungszeichen { #quotes }

//// tab | Test

            File docInfo = new File(destinationDirectory, docInfoName);
            try {
                Files.write(docInfo.toPath(), Collections.singleton(String.format("<meta name=\"adoc-src-path\" content=\"%s\">", relativePath)), StandardOpenOption.CREATE);
            } catch (IOException e) {
                throw UncheckedException.throwAsUncheckedException(e);
            }
        });
    }

        assertSame(testRequestBuffer, requestBuffer);

        // Verify multiple calls return the same instance
        assertSame(requestBuffer, negotiation.getRequestRaw());

        // Verify content is correct
        assertArrayEquals(new byte[] { 0x01, 0x02, 0x03, 0x04 }, requestBuffer);
    }

    @Test
    @DisplayName("getResponseRaw should return the same response buffer")
    void testGetResponseRaw() {

      }
    } catch (Throwable e) {
      throw closer.rethrow(e);
    } finally {
      closer.close();
    }
  }

  private static Manifest manifest(String content) throws IOException {
    InputStream in = new ByteArrayInputStream(content.getBytes(US_ASCII));
    Manifest manifest = new Manifest();
    manifest.read(in);
    return manifest;
  }

  private static File fullpath(String path) {

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2006-11-04
 -----

Maven Toolchain Model

 This is the model for Maven toolchain in <<<org.apache.maven.toolchain>>> package,
 delegating content to {{{../../api/maven-api-toolchain/index.html}Maven 4 API immutable toolchain}}. All the effective model
 building logic from multiple toolchains files is done in {{{../maven-toolchain-builder/}Maven Toolchain Builder}}.

                    "get": {
                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            }
                        },
                        "summary": "Read Current User",
                        "operationId": "read_current_user_users_me_get",