Problem description
In the course of updating TF products to IOTA 1.17.2 the wasm-bindgen crate dependency and wasm-bindgen-cli used in CI workflows have bin pinned to the exact versio 0.2.108.
As been described in product-core issue #101 this forces the used js-sys crate dependency to be pinned to to the exact version = "=0.3.85".
Using later versions of wasm-bindgen or js-sys will probably result in errors as been described in the product-core issue #101.
If these errors occur, the bindings/wasm/identity_wasm/src/bindings/*.rs files need to be migrated to the latest js-sys version, where one of the following alternative options are available:
- Use the context specific
Promise types
- Convert all the context specific types into
Promise<JsValue> instances
See product-core issue #101 for further details.
Feature description
Motivation
Requirements
Open questions (optional)
Are you planning to do it yourself in a pull request?
No
Problem description
In the course of updating TF products to IOTA 1.17.2 the
wasm-bindgencrate dependency and wasm-bindgen-cli used in CI workflows have bin pinned to the exact versio 0.2.108.As been described in product-core issue #101 this forces the used
js-syscrate dependency to be pinned to to the exactversion = "=0.3.85".Using later versions of
wasm-bindgenorjs-syswill probably result in errors as been described in the product-core issue #101.If these errors occur, the
bindings/wasm/identity_wasm/src/bindings/*.rsfiles need to be migrated to the latestjs-sysversion, where one of the following alternative options are available:PromisetypesPromise<JsValue>instancesSee product-core issue #101 for further details.
Feature description
Motivation
Requirements
Open questions (optional)
Are you planning to do it yourself in a pull request?
No