-
Notifications
You must be signed in to change notification settings - Fork 19
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
Properly implement ChargeAssetTXPayment and test it. #90
Conversation
d299a88
to
fa1ca0c
Compare
@@ -73,11 +74,14 @@ public async Task Extrinsic_SubmitAndWatchExtrinsicAsync() | |||
{ | |||
var iType = new BaseVec<U8>(new U8[] { (U8)0x04, (U8)0xFF }); | |||
|
|||
var assetCharge = ChargeAssetTxPayment.NewWithAsset(0, new I32(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.
This requires that we have a liquidity pool on the chain with the asset with id 0 and our native token. On paseo we have that, and this test was run against a paseo node.
@@ -50,7 +51,7 @@ public async Task SetupAsync() | |||
catch (Exception ex) | |||
{ | |||
Console.WriteLine($"Failed to connect to Substrate node: {ex.Message}"); | |||
Assert.Ignore("Skipped test because no active Substrate node was found on 127.0.0.1:9944"); | |||
Assert.Ignore("Skipped test because no active Substrate node was found on 127.0.0.1:9999"); |
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.
The assert message mentioned the wrong port.
Quality Gate passedIssues Measures |
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.
nice
No description provided.