Expose GetMessage in Warp API #1062
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
cam-schultz
requested review from
ceyonur,
darioush and
aaronbuchwald
as code owners
cam-schultz
changed the title
ceyonur
approved these changes
Jan 23, 2024
darioush
approved these changes
Jan 23, 2024
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.
Why this should be merged
Exposes
GetMessagein the Warp API. The use case is for clients (such as awm-relayer) to fetch a Warp message while only needing to know the ID, not the full message bytes.Corresponding coreth PR: ava-labs/coreth#465
How this works
Adds
GetMessageto client.go and service.goHow this was tested
Manually tested via the client in a local deployment
How is this documented
N/A