-
Notifications
You must be signed in to change notification settings - Fork 27
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
Create TeleporterMessenger ABI Go binding #41
Conversation
f2ca4cb
to
23b6eae
Compare
23b6eae
to
728b39c
Compare
Can we make abi_go_bindings.sh generic, so it takes in a file with a list of |
I want to build the contract first, then use the generated files in the |
Yeah, that'll work! |
push: | ||
branches: | ||
- main |
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.
We may only want to do this on pull requests, since the CI job works by (potentially) modifying the branch. I'm sure it's highly unlikely to cause issues, but I'd prefer if we didn't do that on main
in any automated fashion.
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.
My understanding is that every workflow should be run in it's own environment. I don't think this test is really only important in PRs though, so I'm fine with this either way.
scripts/abi_go_bindings.sh
Outdated
cd .. && pwd | ||
) | ||
|
||
DEFAULT_CONTRACT_LIST="TeleporterMessenger" |
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.
Can we add the cross-chain apps to this list, and add the resulting Go bindings to this PR?
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.
added the cross-chain apps. Could you check if I missed anything?
on: | ||
pull_request: | ||
branches: | ||
- "*" |
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.
do we need need to add on push to main?
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.
based on Cam's comments, we may not want to run this on main
in automated fashion
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.
Just one small comment here. Otherwise everything looks great.
push: | ||
branches: | ||
- main |
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.
My understanding is that every workflow should be run in it's own environment. I don't think this test is really only important in PRs though, so I'm fine with this either way.
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.
LGTM!
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.
Let's include bindings for BridgeToken.sol
. Otherwise LGTM
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.
LGTM!
Why this should be merged
TeleporterMessenger
ABI Go bindings.contracts
to generate ABI files, and then generate TeleporterMessenger ABI Go bindings usingabigen
.abi_go_bindings_checker
github action checks if the generated Go bindings are from the latest contractsHow this was tested