import java.net.http.HttpRequest
import java.net.http.HttpResponse


data class GitHubIssueSearchResult(val items: List<GitHubIssue>)


data class GitHubIssue(
    val number: Int,
    val title: String,
    @SerializedName("html_url") val htmlUrl: String
)


const val FIXED_ISSUES_INTRO = "The following issues were resolved:"


@DisableCachingByDefault(because = "Depends on GitHub API")

In this section we'll see how to use other middlewares.

## Adding ASGI middlewares { #adding-asgi-middlewares }

As **FastAPI** is based on Starlette and implements the <abbr title="Asynchronous Server Gateway Interface">ASGI</abbr> specification, you can use any ASGI middleware.

A middleware doesn't have to be made for FastAPI or Starlette to work, as long as it follows the ASGI spec.

The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.

### Format

The format for ADR should follow this template:

```markdown
# ADR-000X - Title

## Status

- REPLACED by ADR-000X on 20YY-MM-DD
- DEPRECATED on 20YY-MM-DD
- ACCEPTED on 20YY-MM-DD
- REJECTED on 20YY-MM-DD
- PROPOSED on 20YY-MM-DD

## Context

        Please open Gradle Native-related issues on [the Gradle Native repository](https://github.com/gradle/gradle-native/issues)

        Provide a brief summary of the issue in the title above
  - type: textarea
    id: current-behavior
    attributes:
      label: Current Behavior
      description: Tell us what happens
    validations:
      required: true
  - type: textarea

API 系统所需的主要特性之一是数据“<dfn title="也称为：编组、转换">序列化</dfn>”，即将代码（Python）中的数据转换为可通过网络发送的形式。例如，将包含数据库数据的对象转换为 JSON 对象、将 `datetime` 对象转换为字符串等。

API 的另一个重要特性是数据校验，确保数据在给定约束下是有效的。例如，某个字段必须是 `int` 而不是任意字符串。这对传入数据尤其有用。

没有数据校验系统的话，你就得在代码里手写所有检查。

这些正是 Marshmallow 要提供的功能。它是个很棒的库，我之前大量使用过。

但它诞生于 Python 类型提示出现之前。因此，定义每个<dfn title="数据应如何构造的定义">模式</dfn>都需要使用 Marshmallow 提供的特定工具和类。

It was created to generate the HTML in the backend, not to create APIs used by a modern frontend (like React, Vue.js and Angular) or by other systems (like <abbr title="Internet of Things">IoT</abbr> devices) communicating with it.

### [Django REST Framework](https://www.django-rest-framework.org/) { #django-rest-framework }

    }

    @Test
    public void test_fields() {
        final Map<String, String[]> fields = Collections.singletonMap("title", new String[] { "test" });
        assertEquals("title:\"test\"", getQuery("", new String[0], fields, Collections.emptyMap(), false));

        final Map<String, String[]> multiFields = Collections.singletonMap("content", new String[] { "value1", "value2" });

For this simple example, we are going to just be completely insecure and return the same `username` as the token.

/// tip

In the next chapter, you will see a real secure implementation, with password hashing and <abbr title="JSON Web Tokens">JWT</abbr> tokens.

But for now, let's focus on the specific details we need.

///

{* ../../docs_src/security/tutorial003_an_py310.py hl[87] *}

/// tip

- string: строка
- tag: мітка
- wildcard: дика карта

### `///` admonitions

- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
- If a title is present, prefer these canonical titles (choose one canonical form where variants exist):

- `/// note | Примітка`
- `/// note | Технічні деталі`
- `/// tip | Порада`
- `/// warning | Попередження`
- `/// info | Інформація`

そして（APIの `/openapi.json` にある）生成されたOpenAPIを見ると、その拡張も特定の *path operation* の一部として確認できます。

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