refactor(parser): use starknetjs parsers to encode decode data

[metalboyrick]

Task name here

Fixes #326 Fixes #319

Types of change

• [ ] Feature
• [ ] Bug
• [X] Enhancement

Comments (optional)

Have not cleaned up yet, but tested with bulletproof contracts, should work with previous data types

TODO:

• [x] Debug page
• [x] useScaffoldReadContract hook
• [x] useScafffoldWriteContract hook
• [x] useScaffoldMultiWriteContract hook
• [ ] ~useScaffoldEventHistory hook~
• [x] Documentation on the hooks input and output - https://github.com/Scaffold-Stark/ss2-docs/pull/38
• [x] Code cleanup of old parsers
• [ ] Update unit tests

[metalboyrick]

Can review first, I will leave it as draft for now @jrcarlos2000 @Nadai2010

[ngjupeng]

there's a bug with tuple unsigned integer

[ngjupeng]

ContractAddress is bigint here

[metalboyrick]

Since I've written some changes for the Address component, this should resolve issue #319 as well

[ngjupeng]

0x0x issue from useScaffoldEventHistory on felt type

[ngjupeng]

issue happen in nested enum

Sample nested enum cairo code:

#[derive(Drop, Serde)]
enum SampleEnum {
    enum1: u256,
    enum2: felt252
}

#[derive(Drop, Serde)]
enum SampleNestedEnum {
    enum1: SampleEnum,
    enum2: felt252
}

#[derive(Drop, starknet::Event)]
pub struct EventWithNestedEnum {
    element1: u256,
    element2: SampleNestedEnum,
}

 fn emit_event_with_nested_enum(
          ref self: ContractState, element1: u256, element2: SampleNestedEnum
      ) {
          self.emit(EventWithNestedEnum { element1, element2 });
      }

[iossocket]

@ngjupeng hi, #339 had fixed the 0x0x event issue, would you mind to check it ?

[ngjupeng]

we need handle this case?

[jrcarlos2000]

we need handle this case?

this used to be handled before @metalboyrick iirc

[metalboyrick]

@jrcarlos2000 @ngjupeng used to be, new changes may have override this, will check

[ngjupeng]

0x is valid input (ignore the gia, it only exist on my local for debug purpose)

[ngjupeng]

u256>

[ngjupeng]

integer type is not working

[ngjupeng]

expect to return as contract format

[iossocket]

will this be a fix for inputting more than one variant for enum form? @metalboyrick

[metalboyrick]

@iossocket yep, enums are supposed to only have one active variant only

[metalboyrick]

yeah but that somehow doesnt work

[iossocket]

does not get this hint?

[metalboyrick]

wait now it works

[metalboyrick]

@iossocket that is the expected one

[metalboyrick]

i tink this breaks down if the enum is nested @iossocket

[iossocket]

is it because one form will only have one errorMessage state, other field item may change it as well?

[metalboyrick]

yep @iossocket fixed this, cc @ngjupeng

[metalboyrick]

expect to return as contract format

@ngjupeng this has been fixed but some output might loook a bit uglier haha

[iossocket]

for the signed integer, starknetjs does not support right now. https://github.com/starknet-io/starknet.js/pull/1177

[ngjupeng]

expect to return as contract format

@ngjupeng this has been fixed but some output might loook a bit uglier haha

this issue existed in tuple and struct also, but it was fixed on array

[metalboyrick]

merging and will record outstanding issues to unblock HH usage