The bug was computing the TypeUsage from the raw schema, before resolving it with multipart semantics.
Covers using the multipart content type with additional properties of a concrete type (string).
This lead to the generator producing half of the code that expected a HTTPBody (a streaming byte type) and another half expected a String, leading to a build failure.
Modifications
First resolve the schema, then calculate the TypeUsage from the resolved schema.
Result
The generator correctly generates this as HTTPBody everywhere now.
Motivation
Fixes #596.
The bug was computing the
TypeUsagefrom the raw schema, before resolving it with multipart semantics.Covers using the multipart content type with additional properties of a concrete type (string).
This lead to the generator producing half of the code that expected a HTTPBody (a streaming byte type) and another half expected a String, leading to a build failure.
Modifications
First resolve the schema, then calculate the
TypeUsagefrom the resolved schema.Result
The generator correctly generates this as
HTTPBodyeverywhere now.Test Plan
Added a unit test to cover this case.