Ingvar Stepanyan
Ingvar Stepanyan
Hm... the last change that transitioned from 0.5 to 0.6 was #40, but I don't see why it would cause this particular breakage.
To be clear, does it break on transition to any 0.6 or only 0.6.3? Did you try pinning exact versions so that Cargo doesn't fetch the latest 0.6.x? That might...
You can see from the Cargo.lock that wasm2 is not 0.6.0 but 0.6.3: https://github.com/vegarringdal/wasm_test/blob/9238388d3217b95fd3cd86bc4a6598c05af72c63/wasm2/Cargo.lock#L87-L89 That's what I suspected and why I mentioned pinning exact version to narrow it down further....
Yeah, no, Cargo auto-updates the version to whatever is compatible according to semver. It's usually the right choice, but not very helpful when debugging an issue.
> Error is after version 0.6.2, update repo What do you mean by "update repo"? Looks like you didn't push any new changes?
That said, if it's 0.6.2+ rather than **after** 0.6.2 (0.6.3+), then I suspect it might be due to this change https://github.com/RReverser/serde-wasm-bindgen/commit/ce7669e1d175d999a733497e87152f55808ee8f2 Not sure if Serde supports field indices in combination...
Yup, looking at generated code from `serde::Deserialize`, the indices it expects don't match the order of fields: ```rust const FIELDS: &'static [&'static str] = &["filter_action", "filtertype", "filter_type", "type"]; ... fn...
Fixed in 0.6.4. Thanks for the report!
None, sorry. It works in tests as expected. It would be helpful if you could provide an isolated minimal repro - e.g. construct a test object using `JsValue` methods or...