-
Notifications
You must be signed in to change notification settings - Fork 132
ABI Reference Types #343
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
ABI Reference Types #343
Conversation
|
nvm... just saw the description |
ahangsu
left a comment
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.
took a quick pass and have some negligible comments, and the only unsettled question is set, I think.
algoidurovic
left a comment
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.
Looks good overall, just a few points I'd like you to address.
Co-authored-by: algoidurovic <91566643+algoidurovic@users.noreply.github.com>
|
one thing to notice, Zeph merged in #322 to feature/abi today, you might want to update too... |
RIght. In particular, it introduced a new member annotation_type that should also be implemented in this PR. |
|
Also, not to hold up the PR, but if simple test cases could be added here, that would be great. I believe that the companion |
|
I think to actually fix tests we need to have a change to the py sdk to support reference types https://github.com/algorand/py-algorand-sdk/blob/master/algosdk/abi/base_type.py#L59 |
That's a good finding. Interestingly, we do have a related test case for handling reference types in method signatures, so I am a bit puzzled by how we pass that test without explicitly handling reference types in @algochoi - it's been a while since you worked on this but maybe you have an insight? |
|
^ we should correspondingly check all other SDK's about unified behavior of type from string function... |
|
@jasonpaulos has shed some light in a separate thread. This is related to a relatively recent change to arc-4 |
The transaction references are handled in the |
|
Completely cheating right now by just skipping round trip tests for the Reference Types. Should we wait to merge this until those are available in the SDK? |
|
Is there a reason that this is basing off of |
I think Ben is testing his code against my router implementation, this PR going into |
39bd2b7 to
4e8efe2
Compare
d046da9 to
e1aba28
Compare
|
superseded by #361 |
Adding reference types to ABI module so we can easily use them in Router.
Targeting abi-router since I'm using it for testing so branched off abi-router
Needs tests but want to make sure this is a reasonable way to attempt this