A bit of a pain point is to parse and format bigInt values to number/strings
We add an 'n' to the end of numbers in the data to handle these numbers as bigInts on the contract. Allowing for really big numbers (common practice in smart contracts) for example 1 gets formatted to '1n' and then parsed back to 1
One way to solve this is to just use numbers on the contract.
Or abstract away the parsing and formatting by checking the datatype and schema and processing the data. This would give artists a more friendlier developer experience as the don't have to worry about types.
A bit of a pain point is to parse and format bigInt values to number/strings
We add an 'n' to the end of numbers in the data to handle these numbers as bigInts on the contract. Allowing for really big numbers (common practice in smart contracts) for example
1gets formatted to'1n'and then parsed back to1One way to solve this is to just use numbers on the contract.
Or abstract away the parsing and formatting by checking the datatype and schema and processing the data. This would give artists a more friendlier developer experience as the don't have to worry about types.