Portanto, você pode declarar "objects" JSON profundamente aninhados com nomes, tipos e validações de atributos específicos.

Tudo isso, aninhado arbitrariamente.

### Defina um sub-modelo { #define-a-submodel }

Por exemplo, nós podemos definir um modelo `Image`:

{* ../../docs_src/body_nested_models/tutorial004_py310.py hl[7:9] *}

### Use o sub-modelo como um tipo { #use-the-submodel-as-a-type }

    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]ide[/\\]ide-plugins[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]plugins[/\\]ide[/\\]eclipse[/\\][^/\\]+"/>

    <!-- Protocol types may only define constants in interfaces -->
    <suppress checks="InterfaceIsTypeCheck"
              files=".*[/\\]tooling-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]tooling[/\\]internal[/\\]protocol.+"/>

SAM Conversions
---------------

When you use Java APIs from Kotlin you can operate on Java interfaces as if they were Kotlin
lambdas. The [feature][java_sams] is available for interfaces that define a Single Abstract Method
(SAM).

But when you use Kotlin APIs from Kotlin there’s no automatic conversion. Code that used SAM lambdas
with OkHttp 3.x: must use `object :` with OkHttp 4.x:

Kotlin calling OkHttp 3.x:

Apenas um detalhe técnico para nerds curiosos. 🤓

Por baixo, na especificação técnica do ASGI, isso é parte do [Protocolo Lifespan](https://asgi.readthedocs.io/en/latest/specs/lifespan.html), e define eventos chamados `startup` e `shutdown`.

/// info | Informação

Você pode ler mais sobre os manipuladores de `lifespan` do Starlette na [Documentação do Lifespan do Starlette](https://www.starlette.dev/lifespan/).

之後只要輸出該資料，即使來源有重覆，也會以唯一元素的 `set` 輸出。

並且也會在註解／文件中相應標示。

## 巢狀模型 { #nested-models }

每個 Pydantic 模型的屬性都有型別。

而該型別本身也可以是另一個 Pydantic 模型。

因此，你可以宣告具有特定屬性名稱、型別與驗證的深度巢狀 JSON「物件」。

而且可以任意深度巢狀。

### 定義子模型 { #define-a-submodel }

例如，我們可以定義一個 `Image` 模型：

{* ../../docs_src/body_nested_models/tutorial004_py310.py hl[7:9] *}

### 將子模型作為型別使用 { #use-the-submodel-as-a-type }

然後把它作為某個屬性的型別使用：

```

因為上傳的檔案是以「表單資料」送出的。

///

## 匯入 `File` { #import-file }

從 `fastapi` 匯入 `File` 與 `UploadFile`：

{* ../../docs_src/request_files/tutorial001_an_py310.py hl[3] *}

## 定義 `File` 參數 { #define-file-parameters }

和 `Body` 或 `Form` 一樣的方式建立檔案參數：

{* ../../docs_src/request_files/tutorial001_an_py310.py hl[9] *}

/// info

`File` 是直接繼承自 `Form` 的類別。

 * implement subtleties of the API improperly.
 *
 * <p><b>Custom implementation</b>: Avoid implementing {@code ListenableFuture} from scratch. If you
 * can't get by with the standard implementations, prefer to derive a new {@code Future} instance
 * with the methods in {@link Futures} or, if necessary, to extend {@link AbstractFuture}.
 *
 * <p>Occasionally, an API will return a plain {@code Future} and it will be impossible to change

{* ../../docs_src/request_files/tutorial001_an_py310.py hl[3] *}

## `File`-Parameter definieren { #define-file-parameters }

Erstellen Sie Datei-Parameter, so wie Sie es auch mit `Body` und `Form` machen würden:

{* ../../docs_src/request_files/tutorial001_an_py310.py hl[9] *}

/// info | Info

`File` ist eine Klasse, die direkt von `Form` erbt.

Ainsi, vous pouvez déclarer des « objets » JSON profondément imbriqués avec des noms d'attributs, des types et des validations spécifiques.

Tout cela, de manière arbitrairement imbriquée.

### Définir un sous-modèle { #define-a-submodel }

Par exemple, nous pouvons définir un modèle `Image` :

{* ../../docs_src/body_nested_models/tutorial004_py310.py hl[7:9] *}

### Utiliser le sous-modèle comme type { #use-the-submodel-as-a-type }

import jakarta.annotation.Resource;

/**
 * API action for admin group management.
 * Provides RESTful API endpoints for managing user group settings in the Fess search engine.
 * Groups define user permissions and access controls for search and administrative functions.
 */
public class ApiAdminGroupAction extends FessApiAdminAction {