iotaledger / iotaledger/identity

[chore]: Migrate identity_wasm/src/bindings to latest js-sys

Open
#1,792 0 comments 0 reactions 0 assignees View on GitHub
Request
Dominant language
Rust
Stars
346
Forks
100
Avg merge
13h 41m
Merged PRs (30d)
2

Description

## Problem description

In the course of updating TF products to [IOTA 1.17.2](https://github.com/iotaledger/identity/pull/1785) 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](https://github.com/iotaledger/product-core/issues/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](https://github.com/iotaledger/product-core/issues/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:
1. Use the context specific `Promise` types
2. Convert all the context specific types into `Promise` instances

See [product-core issue #101](https://github.com/iotaledger/product-core/issues/101) for further details.

### Feature description

## Motivation
---

## Requirements
---

## Open questions (optional)
---

## Are you planning to do it yourself in a pull request?

No

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.