-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
function overriding error #1432
Comments
I may need to use |
Thanks, just happened to me yesterday, blame the SO: https://ethereum.stackexchange.com/a/58341/1210 .'-D |
This code was intended to be used as an internal library, not as a public methods :) |
I ran into a similar issue with a contract function overloading a js object property ( |
@ricmoo this diff should fix the issue. unfortunately i can't open a PR with it right now.
|
@tarrencev Unfortunately, JavaScript `Map cannot be used in v5. In v6, more modern JavaScript features will be employed, but for v5 things must be kept a bit more primitive. |
This should be fixed in 5.5.0. Please try it out and let me know. Thanks! |
This was fixed, so I'll close it. Please re-open or create a new issue if there are any problems. Thanks! :) |
Hey @ricmoo I'm getting same error when I'm deploying contract |
@AyyanNiazi what version of ethers are you using? Can you include a code snippet and the ABI? |
Hi @ricmoo , |
Same issue |
G'day, mates!
While I'm testing Strings.sol library, I got an error with
TypeError: uniqueNames[name_1].push is not a function.
contracts
testing script
I changed a function name from toString to toStrin just for testing. and it works.
function toString(uint256 value) public
So I thought it's because js has the function with the same name.
But although I tried callStatic function to override the js function, it still didn't work.
repeatedly same error
TypeError: uniqueNames[name_1].push is not a function.
But expectedly
const t1 = await test.callStatic["toStrin(uint256)"](123);
with functionfunction toStrin(uint256 value) public
worked.The text was updated successfully, but these errors were encountered: