-
Notifications
You must be signed in to change notification settings - Fork 55
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
[Tests] Transaction submission test suite. The initial attempt at testing all authenticators, payloads and argument types #34
Changes from all commits
fb9b2ba
4096003
397173e
0f72fd1
34774fe
c5a6148
5301a2b
fb1f9c2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -439,7 +439,7 @@ export class MoveObject extends Serializable implements TransactionArgument { | |
if (value instanceof AccountAddress) { | ||
this.value = value; | ||
} else { | ||
this.value = AccountAddress.fromHexInput({ input: value }); | ||
this.value = AccountAddress.fromHexInputRelaxed({ input: value }); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this changing? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would like to use relaxed if we can, I was running into a bunch of errors because of it- basically what we were talking about with daniel I was just putting it here as a fix so I didn't have to fix every instance of an object in the test suite (I wrote it down as feedback/things to think about in the doc), but yea, the issue was I was getting errors from addresses I was getting from the API on chain |
||
} | ||
} | ||
|
||
|
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.
interesting... curios why?
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.
Because I was getting objects from the API, it returned it with no leading 0, meaning I needed to sanitize my input. I then realized I don't see in any case why someone wouldn't want the "relaxed" version when using it as input.
You generally would only use a
MoveObject
to serialize an entry function argument, so the end serialization result is the same regardless of whether or not you input a0x0...
or0x...
, sofromHexInputRelaxed
makes more sense to me than having people run into errors 1/16 times because they didn't expect the address they passed in to to fail the parsing test