-
Notifications
You must be signed in to change notification settings - Fork 26
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
Feature/165 add decode specification v1 #213
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
8859c82
to
b573fe0
Compare
40f444b
to
766d9b3
Compare
…dling for Content component.
…on success only notifications are used.
84de73b
to
113733f
Compare
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 didn't look at the code, but I used the preview website, and it works!
@nevendyulgerov, I'll merge the PR, but could you do a code review and please highlight anything that caught your attention? Also, just a reminder about the issue I raised on the wevm/abitype repository. As such, I am ruling this out for now. |
Summary
Code changes to add support to define a specification to decode ABI standard and non-standard encoded inputs.
Here is a demo recording about the Feature: Demo Video
ps: Interaction with Outputs is out of this feature scope.
Here are the things provided in that feature:
JSON ABI
mode by describing it using Human readable ABI formatABI Parameters
mode by describing the ABI param(s) signature to be used for decoding the data.ABI Parameters
mode; users can also describe how to decode non-standard ABI encoded data by defining byte range slices associated with a name and optionally with a valid ABI type. We're dog fooding by providingSystem Specifications
for all Portals and Relays available at the moment.application-address
andmsg-sender
.JSON ABI
andABI params
.