Fix wasm32 build: un-gate the debug! macro import in smbcloud-network
The debug! logging added to request()/request_login()/parse_error_response() runs on every target, but its import was still cfg-gated to non-wasm32 from when debug! was only used inside a non-wasm-only function. That broke the wasm32-unknown-unknown check and the npm/WASM SDK build.
Seto Elkahfi committed
Jul 21, 2026 at 07:34 UTC
f4c7e783ac88be883ae5695d8180046ca4e6fb36
1 file changed
+1
-4
crates/smbcloud-network/src/network.rs
+1
-4
@@ -1,5 +1,5 @@
1
use {
2
- log::error,
2
+ log::{debug, error},
3
reqwest::{RequestBuilder, Response, StatusCode},
4
serde::de::DeserializeOwned,
5
smbcloud_model::{
@@ -9,9 +9,6 @@ use {
9
},
10
};
11
12
-#[cfg(not(target_arch = "wasm32"))]
13
-use log::debug;
14
-
12
//use std::time::Duration;
13
#[cfg(debug_assertions)]
14
const LOG_RESPONSE_BODY: bool = true; // You know what to do here.