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, we're just sending base64 strings of protobuf data for any events that include data. It's up the the SDK user to parse this data into the correct JS type (using the generated JS protobuf classes).
A better setup would be at least for the SDK to convert to the JS protobuf classes.
Even better would be to create explicit addListener function for each type, removing the general addListener method that takes an event type arg. So for example:
function addThreadAddedListener(listener: (thread: pb.Thread) => void)
The text was updated successfully, but these errors were encountered:
Currently, we're just sending base64 strings of protobuf data for any events that include data. It's up the the SDK user to parse this data into the correct JS type (using the generated JS protobuf classes).
A better setup would be at least for the SDK to convert to the JS protobuf classes.
Even better would be to create explicit
addListener
function for each type, removing the generaladdListener
method that takes an event type arg. So for example:The text was updated successfully, but these errors were encountered: