We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is part of #736
TransactionResult type on the SDK side https://github.com/onflow/flow-go-sdk/blob/master/transaction.go#L620
TransactionResult
TransactionResultResponse message in the Protobuf schema https://github.com/onflow/flow/blob/master/protobuf/flow/access/access.proto#L416
TransactionResultResponse
computation_usage field is missing
computation_usage
The text was updated successfully, but these errors were encountered:
https://github.com/onflow/flow/blob/4998e288f99e963c2e6aa2474bf93c93e228a21b/protobuf/flow/access/access.proto#L416-L427
vs
flow-go-sdk/transaction.go
Lines 620 to 628 in 2689460
The main difference is the SDK is missing these fields: metadata, computation_usage.
metadata
Let's go ahead and add them.
status_code can be ignored.
status_code
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
This is part of #736
TransactionResult
type on the SDK sidehttps://github.com/onflow/flow-go-sdk/blob/master/transaction.go#L620
TransactionResultResponse
message in the Protobuf schemahttps://github.com/onflow/flow/blob/master/protobuf/flow/access/access.proto#L416
computation_usage
field is missingThe text was updated successfully, but these errors were encountered: