所有这些都会被合并并包含到你的 OpenAPI 中，并显示在 API 文档里：

<img src="/img/tutorial/additional-responses/image01.png">

## 组合预定义响应和自定义响应 { #combine-predefined-responses-and-custom-ones }

你可能希望有一些适用于许多*路径操作*的预定义响应，但同时又想把它们与每个*路径操作*所需的自定义响应组合在一起。

在这些情况下，你可以使用 Python 的“解包”`dict` 的技巧 `**dict_to_unpack`：

```Python
old_dict = {
    "old key": "old value",

                    .longOpt("at-file")
                    .hasArg()
                    .desc(
                            "If set, Maven will load command line options from the specified file and merge with CLI specified ones.")
                    .get());
        }
    }

   * invoked in the same order as the underlying service enters those states. Additionally, at most
   * one of the listener's callbacks will execute at once. However, multiple listeners' callbacks
   * may execute concurrently, and listeners may execute in an order different from the one in which
   * they were registered.
   *
   * <p>RuntimeExceptions thrown by a listener will be caught and logged. Any exception thrown

`ModelServer` collates all computation graphs exposed to it (from multiple
`SavedModel`) and executes them in parallel on available executors. Running
TensorFlow in a multitenant design mixes the risks described above with the
inherent ones from multitenant configurations. The primary areas of concern are
tenant isolation, resource allocation, model sharing and hardware attacks.

### Tenant isolation

        // All patterns should be accepted
        assertDoesNotThrow(() -> request.setFileId(allZeros), "Should handle all-zeros file ID");
        assertDoesNotThrow(() -> request.setFileId(allOnes), "Should handle all-ones file ID");
        assertDoesNotThrow(() -> request.setFileId(alternating), "Should handle alternating pattern file ID");
    }

    @Test
    @DisplayName("Should create custom implementation of RequestWithFileId")

        byte[] zeroFileId = new byte[16];
        Smb2FlushRequest zeroRequest = new Smb2FlushRequest(mockConfig, zeroFileId);
        testFileIdInRequest(zeroRequest, zeroFileId);

        // Test with all ones
        byte[] onesFileId = new byte[16];
        Arrays.fill(onesFileId, (byte) 0xFF);
        Smb2FlushRequest onesRequest = new Smb2FlushRequest(mockConfig, onesFileId);
        testFileIdInRequest(onesRequest, onesFileId);

   * under the assumption that for long-running instances, observed
   * contention levels will recur, so the cells will eventually be
   * needed again; and for short-lived ones, it does not matter.
   */

  /**
   * Padded variant of AtomicLong supporting only raw accesses plus CAS. The value field is placed
   * between pads, hoping that the JVM doesn't reorder them.
   *

* Response payloads.

You would also have **inline errors** for everything.

And whenever you update the backend code, and **regenerate** the frontend, it would have any new *path operations* available as methods, the old ones removed, and any other change would be reflected on the generated code. 🤓

            set(value) = Unit

        operator fun String.invoke(p: String, block: String.() -> Unit) = Unit

        ${""/* For Kotlin DSL, we generate sources with collection types mapped to the Kotlin ones. See `org.gradle.kotlin.dsl.internal.sharedruntime.codegen.ApiTypeProviderKt#mappedTypeStrings` */}

これらはすべて結合されて OpenAPI に含まれ、API ドキュメントに表示されます:

<img src="/img/tutorial/additional-responses/image01.png">

## 事前定義レスポンスとカスタムの組み合わせ { #combine-predefined-responses-and-custom-ones }

多くの *path operations* に適用できる事前定義のレスポンスを用意しつつ、各 *path operation* ごとに必要なカスタムレスポンスと組み合わせたい場合があります。

そのような場合、Python の `**dict_to_unpack` による `dict` の「アンパック」テクニックを使えます:

```Python
old_dict = {