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
Since Websockets are built in via web-sys, we only get a JsValue back. I'm being lazy at the moment while fixing #38 and just throwing a string back up through our stack that gives a vague idea of what would be wrong, but it'd be nice if we could somehow get more info into that string than just "url is wrong" or "Server ain't there".
The text was updated successfully, but these errors were encountered:
Since Websockets are built in via web-sys, we only get a JsValue back. I'm being lazy at the moment while fixing #38 and just throwing a string back up through our stack that gives a vague idea of what would be wrong, but it'd be nice if we could somehow get more info into that string than just "url is wrong" or "Server ain't there".
The text was updated successfully, but these errors were encountered: