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

clients/horizonclient: Support paths/strict-send and paths/strict-receive requests. #2237

Conversation

abuiles
Copy link
Contributor

@abuiles abuiles commented Feb 6, 2020

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    semver, or if it's mainly a patch change. The PR is targeted at the next
    release branch if it's not a patch change.

What

Extend horizonclient to support request to /paths/strict-send and /paths/strict-receive

This PR also changes client.Paths to be an alias for client.StrictReceivePaths.

Why

This is a new end-point in Horizon 1.0

Known limitations

[TODO or N/A]

Copy link
Member

@ire-and-curses ire-and-curses left a comment

Choose a reason for hiding this comment

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

This is just strict send right? Could change the PR title to remove "receive"

clients/horizonclient/main.go Outdated Show resolved Hide resolved
clients/horizonclient/strict_send_paths_request.go Outdated Show resolved Hide resolved
Co-Authored-By: Eric Saunders <ire-and-curses@users.noreply.github.com>
@abuiles abuiles changed the title clients/horizonclient: Support strict send receive paths requests. clients/horizonclient: Support strict send paths requests. Feb 6, 2020
@abuiles abuiles changed the title clients/horizonclient: Support strict send paths requests. clients/horizonclient: Support paths/strict-send and paths/strict-receive requests. Feb 6, 2020
Copy link
Member

@ire-and-curses ire-and-curses left a comment

Choose a reason for hiding this comment

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

Looks good. Do we have an example for strict receive? Maybe it needs renaming from the old paths?

@abuiles abuiles merged commit 7e6a2fc into stellar:release-horizonclient-v2.1.0 Feb 6, 2020
@abuiles abuiles deleted the strict-send-strict-receive-paths branch February 6, 2020 23:12
abuiles added a commit that referenced this pull request Feb 19, 2020
…eive requests. (#2237)

* client/horizonclient: Add support for /paths/strict-send.

* Update clients/horizonclient/strict_send_paths_request.go

Co-Authored-By: Eric Saunders <ire-and-curses@users.noreply.github.com>

* Improve docs for StrictSendPathsRequest.

* Add support for paths/strict-receive.

* Use strict receive instead of paths in example.

Co-authored-by: Eric Saunders <ire-and-curses@users.noreply.github.com>
abuiles added a commit that referenced this pull request Feb 25, 2020
…eive requests. (#2237)

* client/horizonclient: Add support for /paths/strict-send.

* Update clients/horizonclient/strict_send_paths_request.go

Co-Authored-By: Eric Saunders <ire-and-curses@users.noreply.github.com>

* Improve docs for StrictSendPathsRequest.

* Add support for paths/strict-receive.

* Use strict receive instead of paths in example.

Co-authored-by: Eric Saunders <ire-and-curses@users.noreply.github.com>
abuiles added a commit that referenced this pull request Feb 29, 2020
…eive requests. (#2237)

* client/horizonclient: Add support for /paths/strict-send.

* Update clients/horizonclient/strict_send_paths_request.go

Co-Authored-By: Eric Saunders <ire-and-curses@users.noreply.github.com>

* Improve docs for StrictSendPathsRequest.

* Add support for paths/strict-receive.

* Use strict receive instead of paths in example.

Co-authored-by: Eric Saunders <ire-and-curses@users.noreply.github.com>
abuiles added a commit that referenced this pull request Apr 7, 2020
…eive requests. (#2237)

* client/horizonclient: Add support for /paths/strict-send.

* Update clients/horizonclient/strict_send_paths_request.go

Co-Authored-By: Eric Saunders <ire-and-curses@users.noreply.github.com>

* Improve docs for StrictSendPathsRequest.

* Add support for paths/strict-receive.

* Use strict receive instead of paths in example.

Co-authored-by: Eric Saunders <ire-and-curses@users.noreply.github.com>
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