Skip to content

caught error information lost #679

Description

@tbrannam

In a development environment, it would be useful to capture the message and perhaps the stack caught by this exception handler.

// Send Serialization Error To Caller

The default message is somewhat helpful, but the error.message information gives additional context which might be helpful in resolving the upstream defect.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions