fix: handle arrays properly in FormData

[omarmciver]

Description

This PR fixes an issue with FormData handling when arrays are involved, particularly for multi-file uploads.

The Problem

When an API endpoint accepts an array of files (or any array in FormData), the current implementation incorrectly converts the entire array to a string representation instead of properly appending each item individually to the FormData object.

Example scenario:

// API expects multiple file attachments
const files = [file1, file2, file3];
api.uploadMultiple({ files });

// Current behavior: FormData contains
// "files" => "[object File],[object File],[object File]" ❌

// Expected behavior: FormData should contain
// "files" => file1
// "files" => file2  
// "files" => file3 ✅

The Solution

This fix modifies the FormData content formatter to:

1. Detect when a property value is an array
2. Iterate through each item in the array
3. Properly append each item individually to FormData
4. Preserve the correct handling of Blob/File types vs other data types

Changes Made

• Updated templates/base/http-clients/fetch-http-client.ejs to handle arrays in FormData
• Added test fixture formdata-arrays.json to verify the fix
• All existing tests pass with updated snapshots

Use Cases

This fix is essential for:

• Multi-file upload endpoints
• Batch document processing APIs
• Any FormData field that accepts multiple values
• Services handling attachments (e.g., agreement management systems)

Testing

• ✅ All existing tests pass
• ✅ Snapshots updated to reflect the new array handling
• ✅ Added test fixture for multi-file upload scenario

Backwards Compatibility

This change is fully backwards compatible:

• Single values continue to work as before
• Arrays are now handled correctly instead of being stringified
• No breaking changes to the API

[changeset-bot]

⚠️ No Changeset found

Latest commit: e4c4bae

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR