Skip to content
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

Boxes: Point go-algorand to boxes_response_rework #210

Merged
merged 1 commit into from
Jul 12, 2022

Conversation

michaeldiamant
Copy link
Contributor

Extends #208 to point go-algorand branch to algorand/go-algorand#4249. Enables SDKs to make corresponding API changes.

Copy link
Contributor

@algochoi algochoi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about we just wait for the boxes_response_rework changes to be merged into the current feature branch? I'm wondering if there is urgency to create a new PR (instead of local branch testing), since we'd have to revert it back when the parent PR needs to be merged in.

@michaeldiamant
Copy link
Contributor Author

How about we just wait for the boxes_response_rework changes to be merged into the current feature branch?

@algochoi Sounds good - I'm on-board to avoid merging the PR. Minimally, I opened the PR for visibility purposes.

@algochoi algochoi merged commit c1eec5e into list-boxes Jul 12, 2022
@algochoi algochoi deleted the boxes_response_rework branch July 12, 2022 15:04
algochoi added a commit that referenced this pull request Jul 15, 2022
* Add path tests for GetApplicationBoxes

* Change step name to include this application and add list box name tests

* Spacing

* Reduce number of redundant steps

* Add query to boxes path test

* Boxes: Point go-algorand to boxes_response_rework (#210)

* Revert back go-algorand testing branch

Co-authored-by: Michael Diamant <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants