Add docs clarifying the wasm32 limitations in the code

cloudflare/src/framework/async_api.rs

@@ -51,7 +51,7 @@ impl Client {
             .default_headers(config.default_headers);
 
         cfg_if! {
-            // There are no timeouts in wasm.
+            // There are no timeouts in wasm. The property is documented as no-op in wasm32.
             if #[cfg(not(target_arch = "wasm32"))] {
                 builder = builder.timeout(config.http_timeout);
             }
@@ -95,7 +95,8 @@ impl Client {
     }
 }
 
-// The async_trait does not work nicely in wasm.
+// The async_trait does not work nicely in wasm. The mapping of Rust Futures to wasm bindgen
+// Promises does not seem to work when the async_trait macro is used: it causes compilation failures.
 #[cfg(not(target_arch = "wasm32"))]
 #[async_trait]
 impl ApiClient for Client {

cloudflare/src/framework/mod.rs

@@ -63,7 +63,9 @@ pub struct HttpApiClient {
 
 /// Configuration for the API client. Allows users to customize its behaviour.
 pub struct HttpApiClientConfig {
-    /// The maximum time limit for an API request. If a request takes longer than this, it will be cancelled.
+    /// The maximum time limit for an API request. If a request takes longer than this, it will be
+    /// cancelled.
+    /// Note: this configuration has no effect when the target is wasm32.
     pub http_timeout: Duration,
     /// A default set of HTTP headers which will be sent with each API request.
     pub default_headers: http::HeaderMap,