// ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    /** createdTime */
    protected Long createdTime;

    /** expiredTime */
    protected Long expiredTime;

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    /** crawlingInfoId */
    protected String crawlingInfoId;

    /** createdTime */
    protected Long createdTime;

### Utiliser l’attribut `app.dependency_overrides` { #use-the-app-dependency-overrides-attribute }

Pour ces cas, votre **FastAPI** application possède un attribut `app.dependency_overrides` ; c’est un simple `dict`.

        super();
    }

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========

    /** The user service for managing user settings. */
    @Resource
    private UserService userService;

    /**

外部プロバイダ自体の動作は一度はテストしたいでしょうが、実行されるすべてのテストで毎回呼び出す必要はありません。

この場合、そのプロバイダを呼び出す依存関係をオーバーライドし、テストのときだけモックユーザーを返すカスタムの依存関係を使えます。

### app.dependency_overrides 属性を使う { #use-the-app-dependency-overrides-attribute }

このような場合のために、**FastAPI** アプリケーションには `app.dependency_overrides` という属性があり、これは単純な `dict` です。

テスト用に依存関係をオーバーライドするには、キーに元の依存関係（関数）を、値にオーバーライドする依存関係（別の関数）を設定します。

すると **FastAPI** は元の依存関係の代わりにそのオーバーライドを呼び出します。

     */
    int CAP_LARGE_WRITEX = 0x8000;
    /**
     * Extended security exchanges are supported capability.
     */
    int CAP_EXTENDED_SECURITY = 0x80000000;

    // file attribute encoding
    /**
     * File is marked read-only
     */
    int ATTR_READONLY = 0x01;
    /**
     * File is marked hidden
     */
    int ATTR_HIDDEN = 0x02;
    /**

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    /** boostExpr */
    protected String boostExpr;

    /** createdBy */
    protected String createdBy;

public class BsDuplicateHostCB extends EsAbstractConditionBean {

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    protected BsDuplicateHostCQ _conditionQuery;
    protected BsDuplicateHostCA _conditionAggregation;

public class BsRelatedQueryCB extends EsAbstractConditionBean {

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    protected BsRelatedQueryCQ _conditionQuery;
    protected BsRelatedQueryCA _conditionAggregation;

Then, when you create an instance of that `Settings` class (in this case, in the `settings` object), Pydantic will read the environment variables in a case-insensitive way, so, an upper-case variable `APP_NAME` will still be read for the attribute `app_name`.

Next it will convert and validate the data. So, when you use that `settings` object, you will have data of the types you declared (e.g. `items_per_user` will be an `int`).