Closed demoray closed 6 months ago
In the future, we should investigate a better way to coalesce multiple errors into a single error. However, this provides a short-term stop gap to address information being swallowed that is needed to address issues.
As indicated in #1543, error details are swallowed when building an aggregate error message.
Currently, we format each of the errors using to_string, which results in the following:
This doesn't help the user understand how to fix the issue.
With this update, we recurse through the error sources, building a more detailed message. This results in:
When printed, this message looks like: