-
Notifications
You must be signed in to change notification settings - Fork 11
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
fix: resolve tx calls based on current runtime #375
fix: resolve tx calls based on current runtime #375
Conversation
add test cases for transferAssets call
added RuntimeCallNotFound BaseErrorEnum updated paraToParaTransferMultiAssets example
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.
Overall, amazing job. Just some small nits but its clearly much cleaner and a nice touch for future work 🚀
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.
There are some errors when I run yarn lint
but they were not introduced from this PR. Just in case you would like to fix them.
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.
Great work! 💯 It is much more clean & clear with the resolveCall
method 👏
It's probably something specific to your local machine since the CI is passing. |
remove unneeded undefined assignment removed named tuple syntax for map types
Description
This PR refactors existing call selection logic into the
resolveCall
method on theAssetTransferAPI
which determines the correct call type and call based on information obtained from the current runtime.Changes
ParaTo,*
SystemTo*
andRelayTo*
XCM directionsxTokens
transfers of parachain native assets (e.g.SDN
->Moonriver
,MOVR
->Bifrost
, etc.) which were previously constructed using onlypolkadotXcm
.closes: #368