REST API TEAL bytes fix #881
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jasonpaulos
commented
Aug 7, 2024
jasonpaulos
commented
Aug 7, 2024
algorandskiy
approved these changes
Aug 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Algod types TEAL byte keys and byte values as strings and base64 encodes them in responses. There was some discussion in algorand/go-algorand#5492 about changing the types on algod, but we decided against it.
This PR updates the types client side so that users don't need to manually decode base64 strings.
A few byte conversion operations were cleaned up as well in the example files.
Relies on algorand/generator#79 to update the generated REST models.