// Ensure bucket exists on first access
            client.ensureBucketExists();

            final List<StorageItem> items = client.listObjects(prefix, fessConfig.getStorageMaxItemsInPageAsInteger());

            for (final StorageItem item : items) {
                final Map<String, Object> map = new HashMap<>();
                map.put("id", item.getEncodedId());

### The resulting response { #the-resulting-response }

If the client requests `http://example.com/items/foo` (an `item_id` `"foo"`), that client will receive an HTTP status code of 200, and a JSON response of:

```JSON
{
  "item": "The Foo Wrestlers"
}
```

                        "properties": {
                            "errors": {
                                "title": "Errors",
                                "type": "array",
                                "items": {"$ref": "#/components/schemas/Error"},
                            }
                        },
                    },
                }
            },
        }

    public void test_selectList_sizeExceedsAvailable() {
        loadTestData();

        DictionaryFile.PagingList<StopwordsItem> result = stopwordsFile.selectList(3, 10);
        // With offset 3 and total 5 items, we should get 2 items
        assertEquals(2, result.size());
        assertEquals(1, result.getCurrentPageNumber()); // First page since we're getting actual results
        assertEquals(10, result.getPageSize());

### 3 단계: *경로 처리* 생성 { #step-3-create-a-path-operation }

#### 경로 { #path }

여기서 "경로"는 첫 번째 `/`부터 시작하는 URL의 뒷부분을 의미합니다.

그러므로 아래와 같은 URL에서:

```
https://example.com/items/foo
```

...경로는 다음과 같습니다:

```
/items/foo
```

/// info | 정보

"경로"는 일반적으로 "엔드포인트" 또는 "라우트"라고도 불립니다.

///

API를 설계할 때 "경로"는 "관심사"와 "리소스"를 분리하기 위한 주요한 방법입니다.

#### 작동 { #operation }

レスポンスオブジェクトにも補完があります:

<img src="/img/tutorial/generate-clients/image05.png">

## タグ付きの FastAPI アプリ { #fastapi-app-with-tags }

実運用ではアプリは大きくなり、*path operation* のグループ分けにタグを使うことが多いでしょう。

例えば **items** 用と **users** 用のセクションがあり、タグで分けられます:

{* ../../docs_src/generate_clients/tutorial002_py310.py hl[21,26,34] *}

### タグ付き TypeScript クライアントの生成 { #generate-a-typescript-client-with-tags }

        urls.add("");
        urls.add("   ");
        urls.add(null);

        Set<RequestData> result = crawlerThread.getAnchorSet(urls);
        assertNull(result, "getAnchorSet should return null when all items are filtered out");
    }

    /**
     * Test getAnchorSet with unsupported object type
     */
    @Test
    public void test_getAnchorSet_withUnsupportedType() {

```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",

    * `url` (**required**): a `str` with the URL for the external documentation.

### Create metadata for tags { #create-metadata-for-tags }

Let's try that in an example with tags for `users` and `items`.

Create metadata for your tags and pass it to the `openapi_tags` parameter:

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

```

</div>

## Проверка { #check-it }

Проверьте работу по адресу вашего Docker-хоста, например: [http://192.168.99.100/items/5?q=somequery](http://192.168.99.100/items/5?q=somequery) или [http://127.0.0.1/items/5?q=somequery](http://127.0.0.1/items/5?q=somequery) (или аналогичный URL вашего Docker-хоста).

Вы увидите что-то вроде:

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