feat: return DecodedMessage when sending PreparedMessage #467
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
neekolas
reviewed
Oct 17, 2023
Deploying with
|
| Latest commit: |
59fcac4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://78e62aaf.xmtp-js.pages.dev |
| Branch Preview URL: | https://rygine-update-prepare-messag.xmtp-js.pages.dev |
rygine
force-pushed
the
rygine/update-prepare-message
branch
from
54233a2 to
59fcac4
Compare
neekolas
approved these changes
Oct 17, 2023
|
🎉 This PR is included in version 11.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
after sending a prepared message, there's no easy way to access the
DecodedMessageof the sent message. this PR returns aDecodedMessagefrom thesendmethod of aPreparedMessage.