## Özellikler { #features }

- **Path Operation Explorer** - Uygulamanızdaki tüm <dfn title="route'lar, endpoint'ler">*path operation*'lar</dfn> için yan panelde bir ağaç görünümü. Herhangi bir route veya router tanımına tıklayarak atlayın.
- **Route Search** - <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>E</kbd> (macOS: <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>E</kbd>) ile path, method veya ada göre arama.

It is a plug-in for many frameworks (and there's a plug-in for Starlette too).

The way it works is that you write the definition of the schema using YAML format inside the docstring of each function handling a route.

And it generates OpenAPI schemas.

That's how it works in Flask, Starlette, Responder, etc.

But then, we have again the problem of having a micro-syntax, inside of a Python string (a big YAML).

## Funktionen { #features }

- Pfadoperation-Explorer – Eine Baumansicht in der Seitenleiste aller <dfn title="Routen, Endpunkte">*Pfadoperationen*</dfn> in Ihrer Anwendung. Klicken Sie, um zu einer beliebigen Route- oder Router-Definition zu springen.

    val address = client.dns.lookup(server.hostName)[0]
    val expectedAddress = InetSocketAddress(address, server.port)
    val event = listener.removeUpToEvent(ConnectionEvent.ConnectStart::class.java)
    assertThat(event.route.socketAddress).isEqualTo(expectedAddress)
  }

  @Test
  @Throws(UnknownHostException::class)
  fun failedConnect() {
    enableTls()
    server.enqueue(MockResponse.Builder().failHandshake().build())

### Azure

- Kubernetes now supports specifying the Resource Group of the Route Table when updating the Pod network route on Azure. ([#75580](https://github.com/kubernetes/kubernetes/pull/75580), [@suker200](https://github.com/suker200))

Örneğin:

```Python
app.add_middleware(MiddlewareA)
app.add_middleware(MiddlewareB)
```

Bu, aşağıdaki çalıştırma sırasını oluşturur:

* **Request**: MiddlewareB → MiddlewareA → route

* **Response**: route → MiddlewareA → MiddlewareB

Bu stack davranışı, middleware'lerin öngörülebilir ve kontrol edilebilir bir sırayla çalıştırılmasını sağlar.

## Diğer Middleware'ler { #other-middlewares }

sts_client = boto3.client(
    'sts',
    region_name='us-east-1',
    use_ssl=False,
    endpoint_url='http://localhost:9000',
)

app = Flask(__name__)


@app.route('/')
def homepage():
    text = '<a href="%s">Authenticate with keycloak</a>'
    return text % make_authorization_url()


def make_authorization_url():
    # Generate a random string for the state parameter

Par exemple :

```Python
app.add_middleware(MiddlewareA)
app.add_middleware(MiddlewareB)
```

Cela aboutit à l’ordre d’exécution suivant :

* **Requête** : MiddlewareB → MiddlewareA → route

* **Réponse** : route → MiddlewareA → MiddlewareB

Ce comportement d’empilement garantit que les middlewares s’exécutent dans un ordre prévisible et contrôlable.

## Autres middlewares { #other-middlewares }

Zum Beispiel:

```Python
app.add_middleware(MiddlewareA)
app.add_middleware(MiddlewareB)
```

Dies führt zu folgender Ausführungsreihenfolge:

* **Request**: MiddlewareB → MiddlewareA → Route

* **Response**: Route → MiddlewareA → MiddlewareB

Dieses Stapelverhalten stellt sicher, dass Middlewares in einer vorhersehbaren und kontrollierbaren Reihenfolge ausgeführt werden.

## Andere Middlewares { #other-middlewares }

                                "content": {"application/json": {"schema": {}}},
                            },
                        },
                        "summary": "Route With Extras",
                        "operationId": "route_with_extras__get",
                        "x-custom-extension": "value",
                    }
                },
            },
        }