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
README.md says that you need to select features as "blocking" to use synchronous feature.
But I think correct option for use synchronous is "reqwest_blocking".
Please change "features = ["blocking"]" to "features = ["reqwest_blocking"]".
Problem section
[dependencies]
## This one is asyncarangors = { version = "0.4", default-features = false }
## This one is synchronousarangors = { version = "0.4", features = ["blocking"], default-features = false }```
The text was updated successfully, but these errors were encountered:
Actually, this is not a mistake. The statement above this examples goes in the following way:
Or if you want to stick with other ecosystem that are not listed in the feature gate,
you can get vanilla arangors without any HTTP client dependency:
This is intended for someone that wants a vanilla arangors and works on their own HTTP implementation. In other words, a clean arangors without any HTTP implmentation. This is useful when someone is dedicated to a ecosystem of HTTP client that is nerither reqwest nor async std.
Currently, out-of-box implementation are of the following:
reqwest_async
reqwest_blocking
surf_async
And among the three features, reqwest_blocking is the only blocking implementation.
README.md says that you need to select features as "blocking" to use synchronous feature.
But I think correct option for use synchronous is "reqwest_blocking".
Please change "features = ["blocking"]" to "features = ["reqwest_blocking"]".
Problem section
The text was updated successfully, but these errors were encountered: