You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current Swift6 generator (and Swift5) with version 7.13.0-snapshot a non-standard class that conforms to Encodable is serialized by first converting it to JSON, and then base64-encoding the result.
Is this being used at all? It would seem much nicer to me if this was done explicitly by a user, and leave only the serialization of Data (byte arrays) to Base64 as a standard. Right now, this behavior is implicit whenever an object is passed into a request that uses it as a query parameter.
The text was updated successfully, but these errors were encountered:
In the current Swift6 generator (and Swift5) with version
7.13.0-snapshot
a non-standard class that conforms to Encodable is serialized by first converting it to JSON, and then base64-encoding the result.Is this being used at all? It would seem much nicer to me if this was done explicitly by a user, and leave only the serialization of Data (byte arrays) to Base64 as a standard. Right now, this behavior is implicit whenever an object is passed into a request that uses it as a query parameter.
The text was updated successfully, but these errors were encountered: