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
Currently, the wasm-pack output for the wasm dir contains a generated types file, but all types are any, while the are of type JsValue in Rust (from the serde_wasm_bindgen library)
Since all types are any currently, we need to check types in the timelock.ts file. This works, but if the input parameters or return types change in the wasm lib, this could potentially be missed in the typescript
it could be verified only at runtime, but it would be optimal to fail at compile time if the types are wrong
it would be ideal if the generated types in timelock_wasm_wrapper.d.ts to map the JsValue to a type (probably UInt8Array).
The text was updated successfully, but these errors were encountered:
wasm
dir contains a generated types file, but all types areany
, while the are of type JsValue in Rust (from the serde_wasm_bindgen library)any
currently, we need to check types in the timelock.ts file. This works, but if the input parameters or return types change in the wasm lib, this could potentially be missed in the typescripttimelock_wasm_wrapper.d.ts
to map the JsValue to a type (probably UInt8Array).The text was updated successfully, but these errors were encountered: