Map array of binary strings to List<MultipartFile>

[joseegman-idoneea]

What

Fixes the mapping of arrays of binary strings (multiple file upload) in the OpenAPI generator. They were generated as List<String> instead of List<MultipartFile>.

Closes #386.

Why

ModelBuilder.processArray(...) resolved the element type of simple array items through MapperUtil.getSimpleType(...), which has no binary detection. A single binary property was already handled correctly (MultipartFile via processStringProperty), but the array path fell through to String.

Change

• ModelBuilder.processArray: detect binary array items with ApiTool.isBinary(items) and map them to TypeConstants.MULTIPART_FILE. ApiTool.isBinary already covers both OpenAPI 3.0 (format: binary) and 3.1 (contentEncoding / contentMediaType). The MultipartFile import is added automatically since getTypeImports walks the inner type of the collection.

Test

• Added an attachments: array of {string, binary} property to the Document schema in the existing testSimpleBuild fixture, and updated the asserted golden DocumentDTO.java to expect List<MultipartFile>.
• Full engine suite green: Tests run: 118, Failures: 0, Errors: 0.

Before / after

// before
private List<String> attachments;
// after
private List<MultipartFile> attachments;

🤖 Generated with Claude Code

Version

Bumps the project version 6.6.0 → 6.6.1 (patch, bugfix) across the engine, Maven plugin and Gradle plugin.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}