-
Notifications
You must be signed in to change notification settings - Fork 10
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
chore: regenerate hooks for its 2.1.0 #499
chore: regenerate hooks for its 2.1.0 #499
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Description
Regenerate abis and hooks for interchain-token-service v2.1.0
Changes
evm
packagesetup-and-tests
gh checks so we can start enabling enforcement gh checks before merging.axelar-registry
deployment so we can start seeing gh checks all green again.Guide to Regenerate ABIs and Hooks for ITS Portal
packages/evm
interchain-token-service
npm packageNote: If that contract contains overloaded functions (same function name, but different signatures) the typescript file will show an error because the same variable names were generated. You have to either rename it or remove the one you didn't use.The codegen will automatically handle overloaded functions by:
Keeping the first overload with original name (e.g., deployRemoteInterchainToken)
Adding numeric suffixes for subsequent overloads (e.g., deployRemoteInterchainToken2)
Using consistent naming across types, encoder functions, and encoder map
apps/maestro
Make sure the following env vars set to the latest contract addresses
The ABIs will be generated based on the contracts in
node_modules/@axelar-network/interchain-token-service
folderHooks will be generated based on generated ABIs in the previous step.
Done 🎉
Hooks and ABIs will be generated under
apps/maestro/src/libs/contracts
folder