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
Currently if you want to return binary data to the client you need to manually encode and decode the data using e.g. base64. This is cumbersome and error prone.
You run into this when using e.g. gRPC or when trying to return some file.
Describe the proposed solution
It would be great to have native support for binary responses. This might also open doors for custom serialization formats -- I would love to have my load function return a protobuf, and transparently receive it on the client in PageData, in a type safe manner.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered:
The problem usually is if we start specifically going out of the way to support one framework/data type then we have to support others. Specifically for things like Uint8Array an issue would be better put in devalue as that's where the serialisation is coming from
Describe the problem
Currently if you want to return binary data to the client you need to manually encode and decode the data using e.g. base64. This is cumbersome and error prone.
You run into this when using e.g. gRPC or when trying to return some file.
Describe the proposed solution
It would be great to have native support for binary responses. This might also open doors for custom serialization formats -- I would love to have my load function return a protobuf, and transparently receive it on the client in
PageData
, in a type safe manner.Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered: