What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
⭐ Feature
🐛 Bug Fix
What is the current behaviour (you can also link to an open issue here)?
Bug
When encoding uintN in tuples and the valueContent is Number, these are always encoded to a uint256 as a 32 bytes long value because of the following line in the code:
What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
⭐ Feature 🐛 Bug Fix
What is the current behaviour (you can also link to an open issue here)?
Bug
When encoding
uintN
in tuples and thevalueContent
isNumber
, these are always encoded to auint256
as a 32 bytes long value because of the following line in the code:https://github.com/ERC725Alliance/erc725.js/blob/06d872baa75fb3bfaac3e51c541e727eb76646e7/src/lib/encoder.ts#L675-L690
Missing Feature
Additionally, there is only support for few
bytesN
types, likebytes2
,bytes4
,bytes8
, etc...What is the new behaviour (if this is a feature change)?
This the padding for the encoding of uintN and bytesN + add support for multiple
bytesN