-
Notifications
You must be signed in to change notification settings - Fork 17
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
Prepare v0.11.0 for release #126
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
0a9ceed
to
337eba1
Compare
Bundle size changes from v0.10.0:
|
paulbellamy
approved these changes
Aug 21, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bro, why you format everything in a release PR 😩
does package.json need |
lol @sreuland I realized this after the fact 🤦 thanks! |
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.
Release Notes
v0.11.0 (diff)
Fixed
SimulateTransactionResponse
's error field now has the correct type (that is,string
: #123).eventsource
,lodash
, and others), lowering overall bundle size (#126).Added
ContractSpec
class to facilitate building native JavaScript structures from custom contract types. Given a specification for the data structure (i.e.xdr.ScSpecEntry[]
), it will interpret the values via the specified type (#115).Breaking Changes
Server.prepareTransaction
now returns aTransactionBuilder
instance rather than an immutableTransaction
, in order to facilitate modifying your transaction after assembling it alongside the simulation response (#127).TransactionBuilder.cloneFrom
) if you need to modify parameters such as the storage access footprint..build()
on the return value.Server.simulateTransaction()
) have been upgraded to parse the base64-encoded XDR automatically. The full interface changes are in the pull request (#127), but succinctly:SimulateTransactionResponse
->RawSimulateTransactionResponse
SimulateHostFunctionResult
->RawSimulateHostFunctionResult
SimulateTransactionResponse
andSimulateHostFunctionResult
include the full, decoded XDR structures instead of raw, base64-encoded strings for the relevant fields (e.g.SimulateTransactionResponse.transactionData
is now an instance ofSorobanDataBuilder
,events
is now anxdr.DiagnosticEvent[]
[try outhumanizeEvents
for a friendlier representation of this field]).SimulateTransactionResponse.results[]
field has been moved toSimulateTransactionResponse.result?
, since there will always be exactly zero or one result.GetTransactionStatus
is now anenum
with actual values rather than atype
(#129).Server.getTransaction()
) have been upgraded to parse the base64-encoded XDR automatically. The full interface changes are in the pull request (#129), but succinctly:GetTransactionResponse
->RawGetTransactionResponse
GetTransactionResponse
is now one ofGetSuccessfulTransactionResponse | GetFailedTransactionResponse | GetMissingTransactionResponse
, which gives proper typing to the interface depending on the response'sstatus
field.*Xdr
properties are now full, decoded XDR structures.returnValue
field which is a decodedxdr.ScVal
, present iff the transaction was a successful Soroban function invocation.Not all schemas have been broken in this manner in order to facilitate user feedback on this approach. Please add your 👍 or 👎 to #128 to vote on whether or not we should do this for the other response schemas.