fix: allow sending strings as encrypted replies in echo_client example #2
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
the `encrypted_reply` function in the echo client example accepts a Message or a string for the reply parameter. But supplying a string caused an error because the variable name `reply` was being reused. This commit introduces a new variable to temporarily hold the reply body, so it can get sent.
|
Whoops, thanks! |
Syndace
added a commit
that referenced
this pull request
Oct 7, 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.
the
encrypted_replyfunction in the echo client example accepts a Message or a string for the reply parameter. But supplying a string caused an error because the variable namereplywas being reused. This commit introduces a new variable to temporarily hold the reply body, so it can get sent.