-
Notifications
You must be signed in to change notification settings - Fork 37
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
Update token transfer to follow specs #551
Update token transfer to follow specs #551
Conversation
assert.equal(transfer.toString(), "100000000000000000"); | ||
}); | ||
|
||
it("should work with NFTs (legacy)", () => { | ||
const identifier = "TEST-38f249"; | ||
const nonce = 1; | ||
const transfer = TokenTransfer.nonFungible(identifier, nonce); | ||
const nonce = 1n; |
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.
Maybe drop the (legacy)
comment, as well?
@@ -85,7 +85,7 @@ export class TokenTransfer { | |||
} | |||
} | |||
|
|||
static newFromEgldAmount(amount: bigint): TokenTransfer { |
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.
maybe this should have been deprecated as well? So it is not breaking.
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 discussed in the office and said it is ok to rename it as it was not long time added
No description provided.