reqwasm icon indicating copy to clipboard operation
reqwasm copied to clipboard

HTTP requests library for WASM Apps

Results 11 reqwasm issues
Sort by recently updated
recently updated
newest added

Yew recently got [Suspense](https://yew.rs/docs/next/concepts/suspense) support and I would like to have reqwasm provide a nice API for API of suspense capable Yew HTTP client. What should the API be?

enhancement
proposal

The problem with `WebSocket` after using `.split()` is that we can no longer access the methods on the `WebSocket`, e.g. `.close()`. This issue would be solved if the `WebSocket` could...

Right now, this library will not work when called from node. This is because uses browser specific APIs. The implementation will be based on the assumption that [`node-fetch` is available...

enhancement

It can be useful to be able to compare the method of a request, e.g. for implementing some common retry logic: ``` if method == http::Method::GET && RETRYABLE_STATUSES.contains(&status) { warn!(...

enhancement
good first issue

Port the now-removed Yew's dashboard example to work with reqwasm

Is there any interest in expanding this crate also to wrap [`web_sys::EventSource`](https://docs.rs/web-sys/0.3.55/web_sys/struct.EventSource.html)? I would imagine taking strong inspiration from how [`web_sys::WebSocket`](https://docs.rs/web-sys/0.3.55/web_sys/struct.WebSocket.html) is wrapped. I am thinking about a future for...

enhancement

The WebSocket futures API does not implement the `Async(Read|Write)` traits. It should.

#4 re-did the websocket API. There should also be a callback based API, alongside the futures one.

When would I use this crate over gloo-net?