Iceman

When using `Vapor.File`, it gets encoded as follows: ``` -----bound5952344343153968676 Content-Disposition: form-data; name="image[data]" -----bound5952344343153968676 Content-Disposition: form-data; name="image[filename]" myfile.jpg ``` However, it seems like @pzmudzinski is expecting it to be encoded...

Sorry, I had missed the extension in Vapor that addresses this issue. With this extension, it would work as expected https://github.com/vapor/vapor/blob/0680f9f6bfab7100cd585b3186740ee7860c983e/Sources/Vapor/Multipart/File%2BMultipart.swift#L4

@pzmudzinski Here is the simple `File.swift` ```swift import Foundation import MultipartKit import NIOFoundationCompat public struct File: Codable, Equatable, Sendable, MultipartPartConvertible { public var filename: String public var data: Data public...

available on 2.1.1

An empty file implies an empty output. Is there a problem, or is it just a matter of feelings?

I want to ensure that first-time users are not confused if no file is generated. If it's a matter of feelings, I'm curious to know if there are others who...

An artifactbundle is required to use mockolo as a buildToolsPlugin. This is an example of releasing mockolo as an artifactbundle. It is working. https://github.com/sidepelican/mockolo/releases/tag/2.0.1 However, it is troublesome to make...

available on 2.1.1

Sorry I forgot launch workflow.

I believe making the definition of dependence implicitly optional might potentially lead to issues.