SDK: Port from certusone sdk to SDKv2 #231
Closed
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
barnjamin
force-pushed
the
barnji/sdkv2
branch
from
543add7
to
83b02a5
Compare
…ests since they're unused in new SDK
barnjamin
force-pushed
the
barnji/sdkv2
branch
from
800a345
to
2ad7c53
Compare
|
replaced by #236 |
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.
Starting to port over to SDKv2 (fka connect-sdk)
The strategy used to port so far is:
The lines changed diff looks a lot more scary than it is, a ton of that is just from the
package-lock.json