Skip to content

Transport-specific associated error types #130

@AlfioEmanueleFresta

Description

@AlfioEmanueleFresta

TransportError is not currently ideal for transport-specific errors. It has generic overly generic variants, and does not include details of the specific underlying cause.

Includes:

  • Replaces TransportError with an associated error type to Channel. For example, CableError.
  • Associated types should support CtapError and PlatformError, eg. implementing From<CtapError> and From<PlatformError>.
  • Replace generic variants (eg. ConnectionLost) in favour of more specific root causes, eg. CableError::HandshakeFailed(snow::Error).
  • CableUxUpdate::Error to use CableError, instead of TransportError.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions