在 OpenAPI 中會以 `anyOf` 定義。

要達成這點，使用標準的 Python 型別提示 [`typing.Union`](https://docs.python.org/3/library/typing.html#typing.Union)：

/// note

在定義 [`Union`](https://docs.pydantic.dev/latest/concepts/types/#unions) 時，請先放置「更具體」的型別，再放「較不具體」的型別。以下範例中，較具體的 `PlaneItem` 置於 `CarItem` 之前：`Union[PlaneItem, CarItem]`。

///

{* ../../docs_src/extra_models/tutorial003_py310.py hl[1,14:15,18:20,33] *}

    FastAPI framework, high performance, easy to learn, fast to code, ready for production
</p>
<p align="center">
<a href="https://github.com/fastapi/fastapi/actions?query=workflow%3ATest+event%3Apush+branch%3Amaster">
    <img src="https://github.com/fastapi/fastapi/actions/workflows/test.yml/badge.svg?event=push&branch=master" alt="Test">
</a>
<a href="https://coverage-badge.samuelcolvin.workers.dev/redirect/fastapi/fastapi">

import org.lastaflute.web.validation.VaMessenger;

import jakarta.annotation.Resource;

/**
 * The base action class for Fess web application.
 * This abstract class provides common functionality for all Fess web actions,
 * including user authentication, validation, message handling, and access context management.
 * It extends LastaFlute's TypicalAction and implements validation and HTML path interfaces.
 *
 * @since 1.0
 */

Si la fonction de dépendance était simplement :

```Python
def get_settings():
    return Settings()
```

nous créerions cet objet pour chaque requête, et nous lirions le fichier `.env` pour chaque requête. ⚠️

Mais comme nous utilisons le décorateur `@lru_cache` au-dessus, l'objet `Settings` sera créé une seule fois, la première fois qu'il est appelé. ✔️

import org.lastaflute.web.util.LaRequestUtil;

import jakarta.annotation.PostConstruct;

/**
 * The helper for user activities.
 * This class provides methods to log user actions such as login, logout, and access.
 * It supports both LTSV and ECS log formats.
 *
 */
public class ActivityHelper {

    /**
     * Default constructor.
     */
    public ActivityHelper() {

</p>
<p align="center">
    FastAPI フレームワーク、高パフォーマンス、学びやすい、素早くコーディングできる、本番運用に対応
</p>
<p align="center">
<a href="https://github.com/fastapi/fastapi/actions?query=workflow%3ATest+event%3Apush+branch%3Amaster">
    <img src="https://github.com/fastapi/fastapi/actions/workflows/test.yml/badge.svg?event=push&branch=master" alt="Test">
</a>
<a href="https://coverage-badge.samuelcolvin.workers.dev/redirect/fastapi/fastapi">

("Commercial Contributor") hereby agrees to defend and indemnify every
other Contributor ("Indemnified Contributor") against any losses,
damages and costs (collectively "Losses") arising from claims, lawsuits
and other legal actions brought by a third party against the Indemnified
Contributor to the extent caused by the acts or omissions of such
Commercial Contributor in connection with its distribution of the Program

## Une application avec des callbacks { #an-app-with-callbacks }

Voyons tout cela avec un exemple.

Imaginez que vous développiez une application qui permet de créer des factures.

Ces factures auront un `id`, un `title` (facultatif), un `customer` et un `total`.

L’utilisateur de votre API (une personne développeuse externe) créera une facture dans votre API avec une requête POST.

Ensuite votre API va (imaginons) :

        // Test with another error status
        setStatus(response, NtStatus.NT_STATUS_INVALID_PARAMETER);
        assertTrue(response.isErrorResponseStatus());
    }

    @DisplayName("Should handle various file actions")
    @ParameterizedTest
    @CsvSource({ "1, FILE_ACTION_ADDED", "2, FILE_ACTION_REMOVED", "3, FILE_ACTION_MODIFIED", "4, FILE_ACTION_RENAMED_OLD_NAME",

			allAtEOF = false
			continue
		}
		storageLogIf(ctx, err)
		return err
	}
	if allAtEOF {
		return io.EOF
	}
	return nil
}

// triggerExpiryAndRepl applies lifecycle and replication actions on the listing
// It returns true if the listing is non-versioned and the given object is expired.
func triggerExpiryAndRepl(ctx context.Context, o listPathOptions, obj metaCacheEntry) (skip bool) {