-
Notifications
You must be signed in to change notification settings - Fork 117
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
PKG -- [transport-grpc] Add blockId to transaction status #1206
Conversation
🦋 Changeset detectedLatest commit: cea93e6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Just the one comment. The update looks good!
payload: {type: "String", value: "Hello, Flow"} | ||
} | ||
] | ||
blockId: |
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.
Nice!
…end-get-block, update send-get-block unit test with collectionGuarantees
…ck-id-transport-grpc
…ck-id-transport-grpc
Just updating docs on this one and it will be ready to go |
689814d
to
ceb92b3
Compare
status: res.getStatus(), | ||
statusString: STATUS_MAP[res.getStatus()], | ||
statusCode: res.getStatusCode(), | ||
errorMessage: res.getErrorMessage(), | ||
events: events.map(event => ({ | ||
type: event.getType(), | ||
transactionId: u8ToHex(event.getTransactionId_asU8(), context), | ||
transactionId: nonEmptyU8ToHex(event.getTransactionId_asU8(), context), |
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.
Is this ever empty? AFAIK events will always have a transactionId
associated. I think we should use the old u8ToHex
in this case?
To be merged after #1205