Add DID Resolution to Node package, and rename Node package #237
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
|
On call, we discussed that this name breaks the convention of other bindings, where |
|
separate tracking issue opened for unrelated iOS CI fail; also, Tiago recommends merging the other node PR (#242) before this one, for merge-conflicts' sake. |
clehner
changed the title
theosirian
approved these changes
Jan 6, 2022
Signed-off-by: Tiago Nascimento <[email protected]>
clehner
force-pushed
the
feat/node-did-resolve
branch
from
6efa8bb
to
2e40c08
Compare
|
Rebased, merging. |
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.
Add
DIDKit.didResolvefunction to the Node.js package/module.