fix: use TransactionPayloadBuilder instead of raw

[victordrnd]

Description

Use of erdjs ContractCallPayloadBuilder instead raw string payload causing conflict when bytes are not even.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

[juliancwirko]

Hi, thanks for the contribution. Can I test it, or will you be working on it further?

[victordrnd]

Hi, Yes you can test it, I may be upgrading some other stuff but not on this branch Le jeu. 6 janv. 2022 à 10:58, Julian Ćwirko ***@***.***> a écrit :

…

Hi, thanks for the contribution. Can I test it, or will you be working on it further? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIW3BHWKEMLCOFTCQTTMNTUUVRTHANCNFSM5LDSHTCA> . You are receiving this because you authored the thread.

[juliancwirko]

I can't add comments in the code, don't know why, but anyway, it should be: .setFunction(new ContractFunction("issueNonFungible")) instead issueSemiFungible

[victordrnd]

Oh yes sorry, bad copy paste

…

On Fri, Jan 7, 2022 at 10:44 AM Julian Ćwirko ***@***.***> wrote: I can't add comments in the code, don't know why, but anyway, it should be: .setFunction(new ContractFunction("issueNonFungible")) instead issueSemiFungible — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIW3BDSFTTNGPX4I6WCOY3UU2YXJANCNFSM5LDSHTCA> . You are receiving this because you authored the thread.Message ID: ***@***.***>