Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WASM Websockets should bubble JS exception back to top #39

Open
qdot opened this issue Dec 21, 2020 · 0 comments
Open

WASM Websockets should bubble JS exception back to top #39

qdot opened this issue Dec 21, 2020 · 0 comments
Assignees
Labels
bug Something isn't working WASM WASM layer for js/ts

Comments

@qdot
Copy link
Member

qdot commented Dec 21, 2020

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".

@qdot qdot added bug Something isn't working WASM WASM layer for js/ts labels Dec 21, 2020
@qdot qdot self-assigned this Dec 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working WASM WASM layer for js/ts
Projects
None yet
Development

No branches or pull requests

1 participant