API: Robust multipart (UTF-8) with Map parameters — fixes #2051 #2054
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR resolves #2051 where SHAFT was unable to handle multipart file uploads when using Map-based parameters, and failed to preserve Arabic text.
Changes
ParametersType.MULTIPART
to explicitly handle multipart form-data.Testing
List<List<Object>>
andMap<String, Object>
parameter formats.Impact
Backwards-compatible; deprecated List API still works.