(Go client) How do I use a MultipartBody with the generated client?

[brandonc]

My open API spec defines a multipart request body this way:

requestBody:
  content:
    multipart/form-data:
      schema:
        type: object
        required:
          - name
          - archive
        properties:
          name:
            type: string
          archive:
            type: string
            format: binary

but the client that is generated does not seem to support a MultipartBody as a request parameter, nor does setting a string as the "archive" field of the generated request body work. It produces this error: only the serialization of multipart bodies is supported with MultipartSerializationWriter Even though I have the multipart serializer registered in my adapter.

How is the multipart body and the generated client interface meant to interact? Thank you very much for your time.

[baywet]

Hi @brandonc
Thank you for using kiota and for reaching out.

Can you please:

• share a minimal reproduction OAI description (complete with just what's needed to reproduce the issue)
• share the resulting POST/PATCH/PUT method

Thanks!

[brandonc]

@baywet Appreciate you taking a look. https://github.com/brandonc/kiota-multipart-repro

You can see the client code I'm trying in main.go as well as spec.yml. The generated client is in generated/, the method request builder is there

[baywet]

Thank you for the additional information.

I was unable to reproduce the issue with the provided description. I noticed that it was generated with kiota 1.18. We've just released 1.19 last week. Can you please try with 1.19?

[brandonc]

I tried with 1.19 but got the same result. I'm not sure what you mean when you say you can't reproduce- the linked repo is the reproduction for both 1.18 and 1.19. I feel like I may be using the API incorrectly but can't find any documentation or examples to clear it up for me. Perhaps there something wrong with the client code?

[baywet]

This is what is incorrect in the repro you've provided

-func (m *EndpointRequestBuilder) ToPostRequestInformation(ctx context.Context, body EndpointPostRequestBodyable, requestConfiguration *EndpointRequestBuilderPostRequestConfiguration)(*i2ae4187f7daee263371cb1c977df639813ab50ffa529013b7437480d1ec0158f.RequestInformation, error) {
+func (m *EndpointRequestBuilder) ToPostRequestInformation(ctx context.Context, body i2ae4187f7daee263371cb1c977df639813ab50ffa529013b7437480d1ec0158f.MultipartBody, requestConfiguration *EndpointRequestBuilderPostRequestConfiguration)(*i2ae4187f7daee263371cb1c977df639813ab50ffa529013b7437480d1ec0158f.RequestInformation, error) {

Now, when I'm debugging locally, I'm not able to reproduce the issue. Meaning that the generation actually updates your repro to the correct thing.

And I believe that's because my local version has this fix #5518
Which was just released 20 minutes ago with version 1.9.1
Can you try again with the new version please?

[brandonc]

Indeed, 1.19.1 worked! I appreciate the fix and the insight.