labels.crawler_title_edit=General Config
labels.schedule=Schedule
labels.enabled=Enabled
labels.day_for_cleanup=Delete old documents
labels.day=days
labels.crawl_button_update=Update
labels.none=None
labels.crawling_thread_count=Concurrent Crawler Config
labels.incremental_crawling=Check Last Modified
labels.search_log_enabled=Search Log
labels.user_info_enabled=User Log
labels.user_favorite_enabled=Favorite Log

from fastapi import FastAPI
from fastapi.testclient import TestClient

app = FastAPI()


@dataclass
class Item:
    name: str
    date: datetime
    price: float | None = None
    owner_ids: list[int] | None = None


@app.get("/items/valid", response_model=Item)
def get_valid():
    return {"name": "valid", "date": datetime(2021, 7, 26), "price": 1.0}


@app.get("/items/object", response_model=Item)

from fastapi import FastAPI
from fastapi.testclient import TestClient
from pydantic import BaseModel

app = FastAPI()


class Item(BaseModel):
    name: str
    price: float | None = None
    owner_ids: list[int] | None = None


@app.get("/items/valid", response_model=Item)
def get_valid():
    return {"name": "valid", "price": 1.0}


@app.get("/items/coerce", response_model=Item)
def get_coerce():

                    }
                    return;
                }
            }
        }

    }

    /*
     * Build a connection. Only one thread will ever call this method at
     * any one time. If this method throws an exception or the connect timeout
     * expires an encapsulating TransportException will be thrown from connect
     * and the transport will be in error.
     */

```Python
say_hi(name=None)  # Bu çalışır, None geçerlidir 🎉
```

İyi haber şu ki, çoğu durumda tip birliklerini (union) tanımlamak için doğrudan `|` kullanabilirsiniz:

```python
def say_hi(name: str | None):
    print(f"Hey {name}!")
```

O parâmetro `name` continua obrigatório (não é opcional) porque não tem valor padrão. Ainda assim, `name` aceita `None` como valor:

```Python
say_hi(name=None)  # Isso funciona, None é válido 🎉
```

A boa notícia é que, na maioria dos casos, você poderá simplesmente usar `|` para definir uniões de tipos:

```python
def say_hi(name: str | None):
    print(f"Hey {name}!")
```

 * an {@code ArrayTable} concurrently and one of the threads modifies its value, there is no
 * guarantee that the new value will be fully visible to the other threads. To guarantee that
 * modifications are visible, synchronize access to the table. Unlike other {@code Table}
 * implementations, synchronization is unnecessary between a thread that writes to one cell and a
 * thread that reads from another.
 *

Раніше ми мали таку анотацію типу:

```Python
q: str | None = None
```

Тепер ми загорнемо її у `Annotated`, і отримаємо:

```Python
q: Annotated[str | None] = None
```

Обидві ці версії означають одне й те саме: `q` — це параметр, який може бути `str` або `None`, і за замовчуванням має значення `None`.

А тепер переходимо до цікавого! 🎉

Nous avions cette annotation de type :

```Python
q: str | None = None
```

Ce que nous allons faire, c’est l’englober avec `Annotated`, de sorte que cela devienne :

```Python
q: Annotated[str | None] = None
```

Les deux versions signifient la même chose, `q` est un paramètre qui peut être une `str` ou `None`, et par défaut, c’est `None`.

Passons maintenant aux choses amusantes. 🎉

        "item_id": 5,
        "item": {
            "name": "Foo",
            "price": 50.5,
            "description": None,
            "tax": None,
        },
        "q": "bar",
    }


def test_post_no_body_q_bar(client: TestClient):
    response = client.put("/items/5?q=bar", json=None)
    assert response.status_code == 200
    assert response.json() == {"item_id": 5, "q": "bar"}