Websocket client onconnect supports neither reply nor close

[lewapkon]

Even though relating to definition it should:

-callback onconnect(websocket_req:req(), state()) ->
    % Simple client: only server-initiated pings will be
    % automatically responded to.
    {ok, state()}
    % Keepalive client: will automatically initiate a ping to the server
    % every keepalive() ms.
    | {ok, state(), keepalive()}
    % Immediately send a message to the server.
    | {reply, websocket_req:frame(), state()}
    % Close the connection.
    | {close, binary(), state()}.

Onconnect supports only {ok, state()} | {ok, state(), keepalive()}.

[sanmiguel]

You're absolutely right, that's a horrible inconsistency. Pretty sure the {close, _, _} should be OK to support, but I'm not sure about {reply, _, _} - it might be too early in the protocol to send data. I need to check... Will get back to you when I find something.