You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2021. It is now read-only.
Is there a way to get a string representation of the error chain without newlines?
For example, this chain:
Error: decoding error
Caused by: cannot decode message payload
Caused by: could not decrypt bytes
...could be written into a string without newlines like this:
Error: decoding error (caused by: cannot decode message payload (caused by: could not decrypt bytes))
The version with newlines is much easier to read when printing it to the terminal, but there are some use cases where a single line is required without newlines.
Single Line
doing something else: doing something: some io error
Multiple Line
Error: doing something else
Caused by: doing something
Caused by: some io error
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a way to get a string representation of the error chain without newlines?
For example, this chain:
...could be written into a string without newlines like this:
The version with newlines is much easier to read when printing it to the terminal, but there are some use cases where a single line is required without newlines.
A workaround could be:
...but that's a bit ugly.
The text was updated successfully, but these errors were encountered: