Let handle_event provide Vec<Value> to self.callback

[kitgxrl]

This allows the client to receive multiple messages in one event if a server sends that way, e.g. 42["chat", user_information, chat_message] is one of many events in my server I'm working with at the moment. Some of this can be chalked up to poor socket design but it's still something socket.io allows.

Unsure if this is the best way to approach this problem! It appears to work in my project fine with little to no issues.

[shenjackyuanjie]

@kitgxrl
have a look at my PR, #392
it's the same thing

[kitgxrl]

@kitgxrl have a look at my PR, #392 it's the same thing

Sorry! Only now noticed that issue was the same thing, thought it was regarding something else! That's my mistake. Closing now.

[shenjackyuanjie]

it's fine, I have notice that you modify the async client and the raw_client would you like to test my PR since I only modify raw_client, async part may not work

[kitgxrl]

Hey! Sorry for late reply. Been busy with personal stuff. I personally don't use async client since the lack of reconnection is kinda a deal breaker since I need to be able to reliably reconnect.