Allow to specify filename as optional parameter to TypedByteArray

[jonnor]

I would expect to be able to use new TypedByteArray(type, bytes, "myfilename.foo") to upload a file multi-part using RetroFit from an in-memory file instead of a File object.

Right now one needs to subclass using work-around described here: #178 (comment)

[rgrinberg]

+1. I've been bitten by this as well

[pepijntb]

+1. Also bitten.

[achuinard]

Yea, I never understood why you couldn't use a TypedByteArray in a multipart file upload. Had the API allowed it, probably would have just figured it out. I'm now using the subclass hack.

[tai2]

👍
achuinard's workaround works fine with current release.
https://gist.github.com/tai2/9b0e1b4f7bc1dd3adce0

[JakeWharton]

TypedByteArray is gone from v2. There's a whole new model of building data with content type and length information from OkHttp. For filename, this is something new and it's being tracked by #1140.