Incorrect type for bytes with web3-1.0.0 target
See original GitHub issueWhen using the Web3 1.0.0 target, it seems that Typechain is generating incorrect types for bytes values.
The generated type is (string | number[])[]
, when I think it should be string | number[]
(no wrapping array). The generated type does not work with Web3.
Happy to try a PR if someone verifies this is indeed a bug 😄
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
InsufficientDataBytes: Tried to read 32 bytes. Only got 0 bytes ...
What was wrong? I have had this specific contract deployed on Ropsten for just over a month but the exact same code has...
Read more >CICS TS for z/OS: Java Applications in CICS - IBM
This PDF tells you how to develop and use Java applications and enterprise beans in CICS. It is for experienced Java application programmers ......
Read more >Fujitsu M10/SPARC M10 Systems Product Notes for XCP ...
Execute the poweron(8) command to power on the target physical partition. ... This problem occurs when the four bytes from the beginning of...
Read more >Untitled
Babbling stage quizlet, To step off on the wrong foot means, Valley of flowers ... Kecelakaan busway, Minimizer bra target, Brad nichols tipton...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 100.0 DAI (100.0 USD @ $1.0/DAI) attached to it.
⚡️ A tip worth 100.00000 DAI (100.0 USD @ $1.0/DAI) has been granted to @touhonoob for this issue from @ceresstation. ⚡️
Nice work @touhonoob! Your tip has automatically been deposited in the ETH address we have on file.