v1.0.0-beta.3
Note: This version is currently only compatible with Stellar networks running the Protocol 20 release candidate such as the current Testnet (using stellar/stellar-xdr@9ac0264).
This is a patch release: please refer to v1.0.0-beta.0 for a complete changelog.
v1.0.0-beta.3
Added
- Responses for
Server.getContractData
andServer.getLedgerEntries
now include anexpirationLedgerSeq
attribute on ledger data entries that have expiry information (#153). - The new
Server._simulateTransaction
method will return the raw response directly from the RPC server rather than parsing XDR fields (#160).
Breaking Changes
- The
stellar-base
dependency has been upgraded to v10.0.0-beta.3 which contains breaking changes related to auth helpers and some bugfixes (#158). - All endpoints will now automatically decode XDR structures whenever possible. In particular,
- For the
Server.getLedgerEntries
response (#154), we parse:entries
is now guaranteed to exist, but it may be emptyentries[i].key
is an instance ofxdr.LedgerKey
- the
entries[i].xdr
field is nowval
, instead entries[i].val
is an instance ofxdr.LedgerEntryData
- For the
Server.sendTransaction
response (#157), we parse:errorResultXdr
is renamed toerrorResult
- If it's present, it's an instance of
xdr.TransactionResult
- For the
Server.getEvents
response (#156), we parse:events[i].contractId
is now an instance ofContract
events[i].topic
is now a list of decodedxdr.ScVal
instancesevents[i].value.xdr
is now remapped directly toevents.value
events[i].value
is a decodedxdr.ScVal
instance
- For the
Server.sendTransaction
response (#157), we parse:errorResultXdr
is nowerrorResult
, a parsed instance ofxdr.TransactionResult
- For the
- If you want to continue to use the raw RPC responses, you can use the
_
-prefixed methods which will return the response directly:Server._getLedgerEntries
Server._sendTransaction
Server._getEvents
Server._simulateTransaction
Server._getTransaction
Full Changelog: v0.11.2...v1.0.0-beta.3