Re-add Resolver API for WASM builds #1526
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wulfraem
added
the
Wasm
- resolver can be created with read-only and with write capable clients - `IotaDocument` now serialize to full serialized `IotaDocument` intead of just the `CoreDocument` part when calling `.to_json()`/`.toJSON()` - this affects the documents resolved via `Resolver` as well - `Resolver` class now accepts generic type parameter to specify the type of the resolved documents
wulfraem
added
the
Added
UMR1352
approved these changes
Feb 18, 2025
bindings/wasm/identity_wasm/examples/src/0_basic/2_resolve_did.ts
Outdated
Show resolved
Hide resolved
bindings/wasm/identity_wasm/src/resolver/wasm_did_resolution_handler.rs
Outdated
Show resolved
Hide resolved
Co-authored-by: Enrico Marconi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re-adds examples for did resolution via
ResolverAPI:0_basic/2_resolve_did.ts1_advanced/4_custom_resolution.tsResolverAPI is re-added, but theattach_iota_handlerandattach_multiple_iota_handlersparts are left out of the WASM build.The Stardust implementation was already not using those two and was directly using a client with respective traits to resolve the DID. Updated implementation follows the same principle, but uses the new API for this.