-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feat/contract packages #57
base: development
Are you sure you want to change the base?
Conversation
Thanks @cryptickoan for the PR Added some minor notes but generally LGTM |
Short documentation for available scripts
"typechain": "^8.1.0", | ||
"typescript": "^4.7.3" | ||
}, | ||
"description": "" |
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.
Might be nice to add a description for each package
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "fuse-v1", | |||
"version": "0.1.0", |
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.
I would prefer to leave this 0.1.0 seeing as it is a moving target. Any patches would then be 0.1.1
, 0.1.2
etc..
Some final minor notes, other than that LGTM, approved 👍 |
This pr will enable package publishing of compiled ABIs under the @fuse-v1 npm name scope. Published contracts are typechain based. I think this would fix contract disparity issues between contract code base and sdk
After changes to any contract are compiled with the interfaces script, we can run
npm run prepare:abis
and then publish the changes by running./abi/scripts/publish.sh