Skip to content

Use String(reflecting: error) for Issue.Kind description instead of "\(error)" #1453

@AFutureD

Description

@AFutureD

Motivation

Errors may contain sensitive data, so many error types intentionally keep description / localizedDescription minimal and place the detailed diagnostics in debugDescription. As a result, when an error occurs we currently log only the non-detailed error text, which often omits the most useful information for troubleshooting. A concrete example is PSQLError where the actionable details are commonly available only via debugDescription.

Proposed solution

public var description: String {

In description method, replace "\(error)" with String(reflecting: error)

Alternatives considered

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions