Move the option under paths section

CreateAPI · Nov 30, 2022 · 23d4a39 · 23d4a39
1 parent 6a4c1b5
commit 23d4a39
Show file tree

Hide file tree

Showing 4 changed files with 26 additions and 25 deletions.
diff --git a/Docs/ConfigOptions.md b/Docs/ConfigOptions.md
diff --git a/Sources/CreateAPI/Generator/Generator+Paths.swift b/Sources/CreateAPI/Generator/Generator+Paths.swift
@@ -690,7 +690,7 @@ extension Generator {
             .other("application/json"),
             .form
         ]
-        if !options.useDataForMultipartFormDataRequestBody {
+        if !options.paths.useDataForMultipartFormDataRequestBody {
             structuredRequestBodySupportedTypes.append(.multipartForm)
         }
         if let (content, contentType) = firstContent(for: structuredRequestBodySupportedTypes) {

diff --git a/Sources/CreateOptions/ConfigOptions.swift b/Sources/CreateOptions/ConfigOptions.swift
@@ -672,6 +672,14 @@ public struct ConfigOptions: ParsableConfiguration {
         ///
         /// </details>
         @Option public var filenameTemplate: String = "%0.swift"
+
+        /// If `false`, CreateAPI generates request body structures for "multipart/form-data" format just like it would for "application/json".
+        /// Otherwise the `body` of the generated `Request` will use `Data`. The default value is `true`.
+        ///
+        /// When using Get and it's `APIClient`, because Multipart Form Data isn't supported from the `Request` `body` property, it is best to leave this option set to `true`.
+        /// If however you have implemented your API Client, and you prefer to use structured `Codable` types to encode a Multipart Form Data request body, setting this value to `false` can be more convenient.
+        /// You might also need to use the [`dataTypes`](#datatypes) option to customise the type used to represent `binary` data.
+        @Option public var useDataForMultipartFormDataRequestBody: Bool = true
     }
 
     @Option public var rename: Rename
@@ -712,14 +720,6 @@ public struct ConfigOptions: ParsableConfiguration {
         /// Rename anonymous collection elements. By default, use a singularized form of the property name
         @Option public var collectionElements: [String: String] = [:]
     }
-
-    /// If `false`, CreateAPI generates request body structures for "multipart/form-data" format just like it would for "application/json".
-    /// Otherwise the `body` of the generated `Request` will use `Data`. The default value is `true`.
-    ///
-    /// When using Get and it's `APIClient`, because Multipart Form Data isn't supported from the `Request` `body` property, it is best to leave this option set to `true`.
-    /// If however you have implemented your API Client, and you prefer to use structured `Codable` types to encode a Multipart Form Data request body, setting this value to `false` can be more convenient.
-    /// You might also need to use the [`dataTypes`](#datatypes) option to customise the type used to represent `binary` data.
-    @Option public var useDataForMultipartFormDataRequestBody: Bool = true
 }
 
 // MARK: - Utilities

diff --git a/Tests/CreateAPITests/GenerateOptionsTests.swift b/Tests/CreateAPITests/GenerateOptionsTests.swift
@@ -395,7 +395,8 @@ final class GenerateOptionsTests: GenerateTestCase {
             name: "edgecases-multipart-formdata",
             configuration: """
             generate: ["paths"]
-            useDataForMultipartFormDataRequestBody: false
+            paths:
+              useDataForMultipartFormDataRequestBody: false
             """
         )
     }