-
Notifications
You must be signed in to change notification settings - Fork 499
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
Horizon v1.0.0 Compatibility #2014
Labels
horizonclient
tag for new horizon client located in clients/horizonclient
Milestone
Comments
@tamirms when you got a sec, can you check if there is anything that we need to do in the java-sdk for the new fields in |
abuiles
changed the title
Update SDKs to support Horizon v0.25.0
Update SDKs to support Horizon v0.26.0
Jan 7, 2020
ire-and-curses
changed the title
Update SDKs to support Horizon v0.26.0
Update SDKs to support Horizon v0.25.0
Jan 15, 2020
ire-and-curses
changed the title
Update SDKs to support Horizon v0.25.0
Update SDKs to support Horizon v1.0
Jan 21, 2020
abuiles
added
the
horizonclient
tag for new horizon client located in clients/horizonclient
label
Jan 22, 2020
abuiles
changed the title
Update SDKs to support Horizon v1.0
Horizon v1.0.0 Compatibility
Jan 22, 2020
I think most of this are done for horizon-client if we branch off release-horizon-0.25.0 |
7 tasks
horizonclient-2.1 is now available. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The upcoming Horizon release is coming, and there are multiple breaking changes plus new features 🎉🎉🎉!
The following are the list of changes required to support this new release:
➕Update
/fee_stats
response.✂ Remove the following fields:
➕Add support for
max_fee
andfee_charged
fields. Each field contains a JSON object that looks like this:See Update /fee_stats documentation. #2140 for more info.
✂ Remove deprecated
fee_paid
field from Transaction response (replace it with thefee_charged
andmax_fee
fields, see #1372).🚨Multiple fields changed from
int64
tostring
. If your SDK has types, they need to be updated. If possible, we recommend implementing backward compatibility support, as we did here.Attribute
offer_id
in manage buy offer and manage sell offer operations.Attribute
offer_id
inTrade
effect.Attribute
id
in Offer resource.Attribute
timestamp
andtrade_count
in Trade Aggregation resource.See Decide on use of int64 in JSON responses. #1609, protocols/horizon/effects: Add UnmarshalJSON to SequenceBumped. #1909, and Support String or Number Unmarshalling in Int64 fields #1912 for more info
🚨 Update operation types to canonical names (if needed) (see protocols/horizon: Apply deprecation on some operation types, updating them to the correct value #2134).
➕Add support for
/accounts
end-point with?signer
and?asset
filters. We recommend a method like.accounts(queryParams)
(see documentation for accounts). clients/horizonclient: Add support for Accounts endpoint. #2229➕Add support for
/offers
end-point with query parameters. We recommend a method like.offers(queryParams)
(see documentation for offers).➕Add support for
/paths/strict-send
end-point. See documentation.We recommend a method like
➕ Add support for
/paths/strict-receive
end-point. See documentation.We recommend a method like:
♻ Regenerate the XDR definitions to include MetaV2 support (also see #1902).
That's it! If you have any questions feel free to ping us on #dev-discussion in Keybase.
The text was updated successfully, but these errors were encountered: