serde-wasm-bindgen
serde-wasm-bindgen copied to clipboard
RReverser
Native integration of Serde with wasm-bindgen
Let say we have a `struct` in Rust as follows: ```rust struct Test { v1: JsValue, v2: JsValue, } let v1 = JsValue::from("hello"); let v2 = JsValue::from("world"); let t =...
This PR makes the README a bit easier to read in plain text, and also replaces the large type conversion bullet-lists with charts. This makes it easier to tell what...
From the README: > and will go away in the future when [reference types](https://github.com/WebAssembly/reference-types) proposal lands natively in Wasm. Given that this has now landed, what needs to be changed...
This allows `Serializer::serialize_maps_as_objects` to actually be used.
The code had been returning errors too early to allow for `deserialize_with` to work. If the visitor does not receive the expected type, it'll try `deserialize_any` so that conversions can...
Added de-serialization from a js_sys::Map. This makes it easier to use data from the result of `DurableObject::load()`. Having #[serde(default)] enables a simple, yet effective data migration.
We just had to swiftly revert our dependency on `serde-wasm-bindgen` back to 0.3.1, as [the introduction of BigInt support](https://github.com/cloudflare/serde-wasm-bindgen/pull/24) makes `BigUint64Array` and `BigInt64Array` be referenced at module scope in the...
After some strange results downstream, I discovered that `#serde(default)` doesn't work. Here are some tests to demonstrate the issue: ```rust #[derive(Deserialize)] struct Person0 { name: String, things: Option, } #[derive(Deserialize)]...
After when going from 0.5 to 0.6 it looks like alias is broken Using: ``` wasm-bindgen = "0.2.91" serde = { version = "1.0.196", features = ["derive"] } serde_json =...
The case that led to me looking into this, is trying to round-trip through serde_wasm_bindgen a serde_json::Value that is a simple map. I also added a test for round-tripping an...
