以上都會被結合並包含在你的 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",

I'll tell you a bit more about these **concepts** here, and that would hopefully give you the **intuition** you would need to decide how to deploy your API in very different environments, possibly even in **future** ones that don't exist yet.

By considering these concepts, you will be able to **evaluate and design** the best way to deploy **your own APIs**.

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

## Combinez les réponses prédéfinies et les réponses personnalisées { #combine-predefined-responses-and-custom-ones }

Vous voulez peut-être avoir des réponses prédéfinies qui s'appliquent à de nombreux *chemins d'accès*, mais vous souhaitez les combiner avec des réponses personnalisées nécessaires à chaque *chemin d'accès*.

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

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

## Combina responses predefinidos y personalizados { #combine-predefined-responses-and-custom-ones }

Es posible que desees tener algunos responses predefinidos que se apliquen a muchas *path operations*, pero que quieras combinarlos con responses personalizados necesarios por cada *path operation*.

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

## Vordefinierte und benutzerdefinierte Responses kombinieren { #combine-predefined-responses-and-custom-ones }

Möglicherweise möchten Sie einige vordefinierte Responses haben, die für viele *Pfadoperationen* gelten, Sie möchten diese jedoch mit benutzerdefinierten Responses kombinieren, die für jede *Pfadoperation* erforderlich sind.

        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);

        // 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")

        void testReadFileIdPatterns() throws Exception {
            // Test with all zeros
            byte[] zeroFileId = new byte[16];
            testFileIdReading(zeroFileId);

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

            // Test with pattern

	retStr := "{"
	retStr = retStr + expirationStr + ","
	retStr += conditionStr
	retStr += "}"

	return []byte(retStr)
}

// newPostPolicyBytesV4 - creates a bare bones postpolicy string with key and bucket matches.
func newPostPolicyBytesV4(credential, bucketName, objectKey string, expiration time.Time) []byte {
	t := UTCNow()
	// Add the expiration date.