</tr>
                                    </thead>
                                    <tbody>
                                    <c:forEach var="data" varStatus="s" items="${dictFiles}">
                                        <tr data-href="${f:h(data.type)}/?dictId=${f:h(data.id)}" role="button" tabindex="0">
                                            <td>${f:h(data.path)}</td>

```

</div>

## Vérifier { #check-it }

Vous devriez pouvoir le vérifier via l'URL de votre conteneur Docker, par exemple : [http://192.168.99.100/items/5?q=somequery](http://192.168.99.100/items/5?q=somequery) ou [http://127.0.0.1/items/5?q=somequery](http://127.0.0.1/items/5?q=somequery) (ou équivalent, en utilisant votre hôte Docker).

Vous verrez quelque chose comme :

```JSON
{"item_id": 5, "q": "somequery"}
```

但本指南會大致示範它們各自的設計用法。

///

### 使用 Pydantic 的 `exclude_unset` 參數 { #using-pydantics-exclude-unset-parameter }

如果要接收部分更新，在 Pydantic 模型的 `.model_dump()` 中使用 `exclude_unset` 參數非常實用。

例如 `item.model_dump(exclude_unset=True)`。

這會產生一個只包含建立 `item` 模型時實際設定過之欄位的 `dict`，不含預設值。

接著你可以用它來生成只包含實際設定（請求中傳來）的資料之 `dict`，省略預設值：

{* ../../docs_src/body_updates/tutorial002_py310.py hl[32] *}

     * for finalName directly in the plugin configuration section. It is also useful to ensure that - for example - a
     * List-typed parameter which expects items of type Artifact doesn't get a List full of Strings.
     *
     * @return <code>true</code> if the user should not be allowed to configure the parameter directly
     */
    boolean readonly() default false;

O objeto `app.webhooks` é na verdade apenas um `APIRouter`, o mesmo tipo que você utilizaria ao estruturar a sua aplicação com diversos arquivos.

///

Note que utilizando webhooks você não está de fato declarando um *path* (como `/items/`), o texto que informa é apenas um **identificador** do webhook (o nome do evento), por exemplo em `@app.webhooks.post("new-subscription")`, o nome do webhook é `new-subscription`.

///

`response_model`, Pydantic model field’ı için declare edeceğiniz aynı tipi alır; yani bir Pydantic model olabilir ama örneğin `List[Item]` gibi Pydantic model’lerden oluşan bir `list` de olabilir.

FastAPI bu `response_model`’i; dokümantasyon, doğrulama vb. her şey için ve ayrıca çıktı verisini **tip tanımına göre dönüştürmek ve filtrelemek** için kullanır.

```JSON hl_lines="22"
{
    "openapi": "3.1.0",
    "info": {
        "title": "FastAPI",
        "version": "0.1.0"
    },
    "paths": {
        "/items/": {
            "get": {
                "summary": "Read Items",
                "operationId": "read_items_items__get",
                "responses": {
                    "200": {
                        "description": "Successful Response",

Например, если клиент попытается отправить query-параметр `tool` с значением `plumbus`, в виде:

```http
https://example.com/items/?limit=10&tool=plumbus
```

То в ответ он получит **ошибку**, сообщающую ему, что query-параметр `tool` не разрешен:

```json
{
    "detail": [
        {
            "type": "extra_forbidden",

This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.

**Please ensure you adhere to every item in this list.**

More info can be found at https://github.com/golang/go/wiki/CommitMessage

+ The PR title is formatted as follows: `net/http: frob the quux before blarfing`
  + The package name goes before the colon

    * `url` (**requis**) : un `str` avec l’URL de la documentation externe.

### Créer des métadonnées pour les tags { #create-metadata-for-tags }

Essayons cela avec un exemple de tags pour `users` et `items`.

Créez des métadonnées pour vos tags et transmettez-les au paramètre `openapi_tags` :

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}