-
Notifications
You must be signed in to change notification settings - Fork 765
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
Monorepo Wallet Library Integration #2729
Conversation
Reason is KryptoKit requires 'aesjs', which adds extra 70k of code when browserified. This change could be reverted once the code can be replaced with 'crypto'.
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the tests are passing. This looks great!
@@ -0,0 +1,36 @@ | |||
name: Build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this workflow move into our monorepo, instead of reside into packages/wallet
?
Ok it seems like our CI does not run the wallet build CI, we should add. |
Nvm thats part of #2731 |
This PR integrates the ethereumj-wallet library into the monorepo, creating a dedicated folder
packages/wallet
with the corresponding source and other files.ATTENTION!!!
THIS NEEDS TO BE MERGED WITH A MERGE COMMIT!!!
DO NOT SQUASH!!!!!
Integration follows the path from e.g. #971, so creating a branch on the original repository, move all files there to the
packages/wallet
folder already and then add the wallet repository locally to the monorepo as a Git remote and merge the wallet branch to a monorepo branch (so, this one:monorepo-add-wallet
) with the flag--allow-unrelated-histories
.So one main goal with the procedure is to preserve the git commit history, this has been proven to work various times already though. For this round I have also tested this locally.
WIP, this needs some various adoptions still.