* When the non-null default value for a particular parameter type cannot be provided by {@code
 * NullPointerTester}, the caller can provide a custom non-null default value for the parameter type
 * via {@link #setDefault}.
 *
 * @author Kevin Bourrillion
 * @since 10.0
 */
@GwtIncompatible
@J2ktIncompatible
@NullMarked

```Python hl_lines="30-31" title="app/routers/items.py"
{!../../docs_src/bigger_applications/app/routers/items.py!}
```

/// tip | Tipp

Diese letzte Pfadoperation wird eine Kombination von Tags haben: `["items", "custom"]`.

Und sie wird auch beide Responses in der Dokumentation haben, eine für `404` und eine für `403`.

///

## Das Haupt-`FastAPI`.

Sehen wir uns nun das Modul unter `app/main.py` an.

          <description>
            The configurator type to use when injecting parameter values into this Mojo. The value is normally deduced
            from the Mojo's implementation language, but can be specified to allow a custom ComponentConfigurator
            implementation to be used.
          </description>
        </field>
        <field>
          <name>composer</name>
          <version>1.0.0/1.1.0</version>

```Python hl_lines="30-31" title="app/routers/items.py"
{!../../docs_src/bigger_applications/app/routers/items.py!}
```

/// tip | Подсказка

Последний *эндпоинт* будет иметь следующую комбинацию тегов: `["items", "custom"]`.

А также в его документации будут содержаться оба ответа: один для `404` и другой для `403`.

///

## Модуль main в `FastAPI`

Теперь давайте посмотрим на модуль `app/main.py`.

   * description of the returned view's behavior.
   *
   * <p><b>Warning:</b> {@code Range}s always represent a range of values using the values' natural
   * ordering. {@code NavigableSet} on the other hand can specify a custom ordering via a {@link
   * Comparator}, which can violate the natural ordering. Using this method (or in general using
   * {@code Range}) with unnaturally-ordered sets can lead to unexpected and undefined behavior.
   *

This release contains changes that address the following vulnerabilities:

### CVE-2022-3162: Unauthorized read of Custom Resources

A security issue was discovered in Kubernetes where users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group they are not authorized to read.

**Affected Versions**:

- API paging is now enabled for custom resource definitions, custom resources and APIService objects. ([#67861](https://github.com/kubernetes/kubernetes/pull/67861), [@liggitt](https://github.com/liggitt))

and specified for [deprecated versions of custom resources](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#version-deprecation).

### Avoiding permanent beta

    server.enqueue(
      MockResponse(
        headers = headersOf("Content-Encoding", "custom"),
        body = "ABCDE",
      ),
    )
    val response =
      getResponse(
        Request
          .Builder()
          .url(server.url("/"))
          .header("Accept-Encoding", "custom")
          .build(),
      )

  @Test fun unknownFrameTypeSkipped() {
    writeMedium(frame, 4) // has a 4-byte field
    frame.writeByte(99) // type 99
    frame.writeByte(FLAG_NONE)
    frame.writeInt(expectedStreamId)
    frame.writeInt(111111111) // custom data
    reader.nextFrame(requireSettings = false, BaseTestHandler()) // Should not callback.
  }

  @Test fun onlyOneLiteralHeadersFrame() {
    val sentHeaders = headerEntries("name", "value")