Closed frantuma closed 2 months ago
@frantuma Cool! one question: my current workaround for this issue is to annotate all endpoints returning byte[] as returning byte. Is this change compatible with this workaround? or will I need to pay attention when upgrading to the next version?
thanks a lot
@RInverid it should be ok
@frantuma When we can expect this PR to be included in the next release?
Thanks
Simone
@spulci released 2.2.22
Includes and replaces https://github.com/swagger-api/swagger-core/pull/3955
Closes https://github.com/swagger-api/swagger-core/issues/3944 and https://github.com/swagger-api/swagger-core/issues/3511.
See also https://github.com/swagger-api/swagger-parser/issues/1630
It introduces binary-string-conversion env or system variable, allowing to define behavior for resolution and conversion of byte arrays:
binary-string-conversion = base64 : resolves into ByteArraySchema/BinarySchema using Base64 for casting/conversion binary-string-conversion = string-schema : resolves into StringSchema