fix: show actual response status field #197
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
Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron
force-pushed
the
feature/fix_error_msg_1
branch
from
4bf2456
to
0e037cc
Compare
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.
Summary
Show the actual response status code, instead of
{error.status:?}.Currently, when a remote call fails with a client or server error, it shows a response error with the following message:
However, I do believe the actual intention (and what would be helpful), is to show the actual status code, instead of the literal string:
{error.status:?}.This PR fixes this issue, so that the error code gets shown.
Release Note
Fix an issue where, instead of the actual error code, the literal string
{error.status:?}was shown.Documentation