In this case, if you go to:

```
http://127.0.0.1:8000/items/foo?short=1
```

or

```
http://127.0.0.1:8000/items/foo?short=True
```

or

```
http://127.0.0.1:8000/items/foo?short=true
```

or

```
http://127.0.0.1:8000/items/foo?short=on
```

or

```
http://127.0.0.1:8000/items/foo?short=yes
```

)


THIS_DIR = Path(__file__).parent.resolve()


def pytest_collection_modifyitems(config, items: list[pytest.Item]) -> None:
    if sys.platform != "win32":
        return

    for item in items:
        item_path = Path(item.fspath).resolve()
        if item_path.is_relative_to(THIS_DIR):
            item.add_marker(skip_on_windows)


@pytest.fixture(name="runner")
def get_runner():
    runner = CliRunner()

from pydantic.v1 import BaseModel


class Item(BaseModel):
    name: str
    description: str | None = None

# user properties at the very beginning of Maven's boot process.
#

# Comma-separated list of files to include.
# Each item may be enclosed in quotes to gracefully include spaces. Items are trimmed before being loaded.
# If the first character of an item is a question mark, the load will silently fail if the file does not exist.
${includes} = ?"${maven.user.conf}/maven-user.properties", \

                elevateWord.getTags(), elevateWord.getRoles());
        settings.elevateWord().add(normalized);
        if (apply) {
            final SuggestItem item = normalized.toSuggestItem();
            return indexingOps.index(index, item, badWordsSupplier.get());
        }
        return new SuggestIndexResponse(0, 0, null, 0);
    }

    /**
     * Deletes an elevate word.
     *

                                                key="labels.reqheader_web_crawling_config"/></th>
                                        <td><c:forEach var="item" items="${webConfigItems}">
                                            <c:if test="${webConfigId==item.value}">${f:h(item.label)}</c:if>
                                        </c:forEach> <la:hidden property="webConfigId"/></td>
                                    </tr>

							</h1>
						</div>
						<div class="col-sm-6">
							<ol class="breadcrumb float-sm-right">
								<li class="breadcrumb-item"><la:link href="/admin/storage/">
										<la:message key="labels.crud_link_list" />
									</la:link></li>
								<li class="breadcrumb-item active"><la:message key="labels.crud_link_edit" /></li>
							</ol>
						</div>
					</div>
				</div>
			</div>
			<section class="content">

</details>

### 확인하기 { #check-it }

브라우저로 [http://127.0.0.1:8000/items/5?q=somequery](http://127.0.0.1:8000/items/5?q=somequery)를 열어보십시오.

아래의 JSON 응답을 볼 수 있습니다:

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

여러분은 벌써 API를 만들었습니다:

* _경로_ `/` 및 `/items/{item_id}`에서 HTTP 요청 받기.
* 두 _경로_ 모두 `GET` 연산(HTTP _메소드_ 로 알려진)을 받습니다.
* _경로_ `/items/{item_id}`는 `int`형 이어야 하는 _경로 매개변수_ `item_id`를 가지고 있습니다.

3. The `Author` dataclass includes a list of `Item` dataclasses.

4. The `Author` dataclass is used as the `response_model` parameter.

5. You can use other standard type annotations with dataclasses as the request body.

    In this case, it's a list of `Item` dataclasses.

6. Here we are returning a dictionary that contains `items` which is a list of dataclasses.

                                                   styleClass="form-control">
                                            <c:forEach var="item" items="${protocolSchemeItems}">
                                                <la:option value="${f:u(item.value)}">${f:h(item.label)}</la:option>
                                            </c:forEach>
                                        </la:select>