Skip to content

Conversation

@tconley1428
Copy link
Contributor

What was changed

Add method for acquiring application error details with a type hint

Why?

Checklist

  1. Closes [Bug] Add ability to obtain ApplicationError details with type hint #1262

  2. How was this tested:

  1. Any docs updates needed?

@tconley1428 tconley1428 marked this pull request as ready for review January 20, 2026 18:08
@tconley1428 tconley1428 requested a review from a team as a code owner January 20, 2026 18:08
"""User-defined details on the error."""
return self.details_with_type_hints()

def details_with_type_hints(
Copy link
Member

@cretz cretz Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hrmm, I can't find a similar comment I made for this elsewhere, but basically I think we should:

  • Deprecate the details property
  • Add a details_len() method
  • Add a get_detail/detail method here that accepts kwargs index (default 0) and type hint (default Any)
    • If details is not None then this was user created and type must be a supertype of what is in details at that index, then return it
    • If details is None then this was created with payloads and _payloads should not be None and you can perform conversion on the detail at that index (or fail w/ index out of bound)
  • Do the same for activity.Info.heartbeat_details

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Add ability to obtain ApplicationError details with type hint

4 participants