-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix(rpc): return error instead of wrong operation type in otterscan API #10896
Conversation
blocked by alloy-rs/alloy#1288 |
088dbc2
to
dbfef33
Compare
Doesn't have to be blocked on it, I doubt otterscan will add a new variant for this since it's essentially the same as create |
6067378
to
93a3ef1
Compare
cargo update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is useful because mostlikely the user doesn't care whether the create was done in eof or not, as far as otterscan is concerned this is also just a Create and we shouldn't fail, so mapping this to a regular create variant makes more sense here until there's a spec update for otterscan
cool then we can add the variant to the otterscan type in alloy |
Return error instead of wrong operation type for EOFCREATE in otterscan API, until otterscan API has EOF support. Likely users will believe that there is smthg wrong with the node rather than RPC response if we return the wrong operation type.