int inside of a record seems to be returned as string instead of number

[thepiwo]

No description provided.

[marc0olo]

are you sure? I think I tested that some time ago and always received BigInt as representation for int

[thepiwo]

just noticed using the call-data lib in an existing test setup

sure, when its supposed to be like this thats fine for me

[marc0olo]

so you are referring to the current state of this branch: https://github.com/aeternity/aepp-sdk-js/tree/feature/calldata ?

and using this branch brings you the result on the right whereas in the past you got the result on the left? (screenshot)

[marc0olo]

I am asking because maybe the SDK does some transformation here. I am pretty sure the calldata lib uses BigInt according to the tests I ran few weeks ago.

cc @davidyuk @mradkov

[dincho]

Please provide minimal reproducible example using the calldata lib public API only. As @marc0olo mentioned this lib works with native BigInts: https://github.com/aeternity/aepp-calldata-js/blob/master/tests/Decoder.js#L307

[davidyuk]

I had a similar issue in sdk tests, it is probably because chai doesn't support BigInt well

[marc0olo]

@davidyuk but that's an issue of the SDK then, right? then it's related to this again, isn't it? => aeternity/aepp-sdk-js#1290

[davidyuk]

but that's an issue of the SDK then, right?

Nope, sdk doesn't modify BigInts returned from calldata (I planning to keep it as it is), the bug is in chai package that probably Philipp uses

[marc0olo]

@thepiwo did you use chai ? can you confirm and close the issue?