Skip to content
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

Wasm Bindings for JWT Presentations #1179

Merged
merged 34 commits into from
Jun 11, 2023
Merged

Wasm Bindings for JWT Presentations #1179

merged 34 commits into from
Jun 11, 2023

Conversation

abdulmth
Copy link
Contributor

@abdulmth abdulmth commented Jun 6, 2023

Description of change

Add wasm bindings for JWT presentation and its validation.

Links to any relevant issues

#1151
#1175

Type of change

Add an x to the boxes that are relevant to your changes.

  • Bug fix (a non-breaking change which fixes an issue)
  • Enhancement (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Fix

@abdulmth abdulmth self-assigned this Jun 6, 2023
@abdulmth abdulmth added Wasm Related to Wasm bindings. Becomes part of the Wasm changelog Added A new feature that requires a minor release. Part of "Added" section in changelog labels Jun 6, 2023
@abdulmth abdulmth changed the title [WIP] Wasm Bindings for JWT Presentations Wasm Bindings for JWT Presentations Jun 6, 2023
Copy link
Contributor

@PhilippGackstatter PhilippGackstatter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

assert.deepStrictEqual(customVerifier.verifications(), 2);
assert.deepStrictEqual(credentialRetrievedCustom.toJSON(), credential.toJSON());
assert.deepStrictEqual(decoded.credentials()[0].credential().toJSON(), credential.toJSON());
assert.equal(decoded.expirationDate()?.toString(), expirationDate?.toString());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
assert.equal(decoded.expirationDate()?.toString(), expirationDate?.toString());
assert.equal(decoded.expirationDate()!.toString(), expirationDate!.toString());

We know those properties are set, so we shouldn't use ?, right? If they don't end up being set, we would like the test to fail.

@abdulmth abdulmth merged commit 36606a8 into main Jun 11, 2023
@abdulmth abdulmth deleted the feat/jwt-presentation-wasm branch June 11, 2023 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Added A new feature that requires a minor release. Part of "Added" section in changelog Wasm Related to Wasm bindings. Becomes part of the Wasm changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants