Skip to content

refactor: Unify error boundary for account-info blocking work  #96

@ovitrif

Description

@ovitrif

One follow-up thought: run_account_info_blocking looks like the right pattern for the other onchain BDK/Electrum blocking calls too, like get_account_info, get_transaction_history, and get_transaction_detail. Could we apply it there in a follow-up so this module has one consistent error boundary for account-info blocking work?

Originally posted by @ben-kaufman in #95 (review)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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