forked from iotaledger/identity.rs
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstream merge #9
Merged
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
* Add serialization for usize as string in StatusList2021Entry * Add test for statusListIndex serialization in StatusList2021Entry * chore: downgrade rust version for wasm crate * chore: fmt
* add support for percent encoded characters in did url components * cargo clippy * cargo clippy * wasm cargo clippy * review comments * Update identity_did/src/did_url.rs Co-authored-by: wulfraem <[email protected]> * fmt & clippy --------- Co-authored-by: wulfraem <[email protected]>
* Resolver trait and CompoundResolver macro * invert Resolver type parameters * associated type Target instead of type parameter T * fix type issue in #[resolver(..)] annotation, support for multiple resolvers with the same signature * resolver integration * feature gate resolver-v2 * structures & basic operations * SdJwtVc behaves as a superset of SdJwt * issuer's metadata fetching & validation * type metadata & credential verification * change resolver's constraints * integrity metadata * display metadata * claim metadata * fetch issuer's JWK (to ease verification) * validate claim disclosability * add missing license header * resolver change, validation * SdJwtVcBuilder & tests * validation test * KB-JWT validation * review comment * undo resolver-v2 * fix CI errors * make clippy happy * add missing license headers * add 'SdJwtVcBuilder::from_credential' to easily convert into a SD-JWT VC * cargo clippy * fix wasm compilation errors, clippy * WASM Bindings for SD-JWT VC (iotaledger#1493) * reworked sd-jwt bindings * SdJwtVc WASM bindings * small example, many small fixes * example & small fixes * restore package.json * Update bindings/wasm/src/sd_jwt_vc/builder.rs Co-authored-by: wulfraem <[email protected]> * Update bindings/wasm/src/sd_jwt_vc/claims.rs Co-authored-by: wulfraem <[email protected]> * Update bindings/wasm/src/sd_jwt_vc/metadata/vc_type.rs Co-authored-by: wulfraem <[email protected]> * Update bindings/wasm/src/sd_jwt_vc/sd_jwt_v2/builder.rs Co-authored-by: wulfraem <[email protected]> * Update bindings/wasm/src/sd_jwt_vc/sd_jwt_v2/sd_jwt.rs Co-authored-by: wulfraem <[email protected]> * review comments --------- Co-authored-by: wulfraem <[email protected]> * Apply suggestions from code review Co-authored-by: wulfraem <[email protected]> * review comments * clippy & fmt * clippy & fmt * dprint fmt --------- Co-authored-by: wulfraem <[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.
Description of change
Please write a summary of your changes and why you made them.
Links to any relevant issues
Be sure to reference any related issues by adding
fixes issue #
.Type of change
Add an
x
to the boxes that are relevant to your changes.How the change has been tested
Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
Change checklist
Add an
x
to the boxes that are relevant to your changes.