softprops / again

♻️ Retry faillible Rustlang std library futures

Hello 🍦

I'm on a curiosity voyage and these keys are my paddles 👨‍💻

---

Rules of the road

• What you learn while building is always more important than what you build
• Be humble
• Don't give up the ship
• Learn with others when you can
• You are not the code you write
• Joy is experiencing life with others, spark it
• Code is not an asset, it's a liability
• It's okay to color out side the lines
• It's okay to come a purler
• Don't let perfect be the enemy of good
• It probably needs more tests...

again's Issues

New release?

This change seems to be not released #11. It is possible to publish a new release?

Make wasm-timer a dependency only if wasm feature is needed

setup better ci integration tests for wasm

At the moment we're only doing simple built tests which is helpful but not ideal as some transient crates compile with noop impl on wasm targets that fail at runtime. Let's set up something a little more complete to protect against regressions

complie error

--> src/main.rs:7:10
|
7 | #[tokio::main]
| ^^^^ could not find main in tokio

error[E0423]: expected value, found struct RetryPolicy
--> src/main.rs:10:18
|
10 | let policy = RetryPolicy.exponential(Duration::from_millis(200))
| ^^^^^^^^^^^------------
| |
| help: use the path separator to refer to an item: RetryPolicy::exponential

warning: unused #[macro_use] import
--> src/main.rs:1:1

Panic 'not in a browser' when runs in webworker

Probably related to tomaka/wasm-timer#12
github.com-1ecc6299db9ec823/wasm-timer-0.2.5/src/wasm.rs:59:14

Add support for Retry-After header

I am not sure how this should be implemented but it would be nice to be able to mutate the duration upon receiving Retry-After header.