-
-
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
Contract staticCall is in implemented as callStatic #924
Labels
documentation
Documentation related issue.
fixed/complete
This Bug is fixed or Enhancement is complete and published.
Comments
This was referenced Jul 2, 2020
Oh, I will fix the docs. The API can no longer be changed as v5 is released and in the wild. I’ll get to this today. :) |
zemse
added a commit
to zemse/TypeChain
that referenced
this issue
Jul 3, 2020
zemse
added a commit
to zemse/TypeChain
that referenced
this issue
Jul 3, 2020
ricmoo
added a commit
that referenced
this issue
Jul 5, 2020
I've updated the docs and published them. Thanks! :) |
softdevpro7
added a commit
to softdevpro7/TypeChain
that referenced
this issue
Nov 24, 2022
SuperStar0106
added a commit
to SuperStar0106/Ganache
that referenced
this issue
Jul 1, 2023
486xtm
pushed a commit
to 486xtm/chain-type
that referenced
this issue
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Documentation related issue.
fixed/complete
This Bug is fixed or Enhancement is complete and published.
Hi @ricmoo, in the actual contract object I am seeing this as
callStatic
?References: #395, documentation
ethers.js/packages/contracts/src.ts/index.ts
Lines 608 to 613 in d817416
I think renaming the implemented
callStatic
tostaticCall
might cause people who already have implemented that (might be less though shouldn't be a problem what do you think?), or we can keepcallStatic
and updating the docs with the correct method.Since I had blindly added the
staticCall
to the typechain ethers v5 target, now that I am actually using this part, I encountered this problem. If we are keepingcallStatic
then I will need to update it there.The text was updated successfully, but these errors were encountered: