temporalio / temporalio/sdk-python
[Bug] Add ability to obtain `ApplicationError` details with type hint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 241
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 55
Description
Describe the bug
For users of deserialized ApplicationError, today we only offer the deserialized details in raw Python form (e.g. dicts and such). For ApplicationErrors that are deserialized, we should make the details property lazy, have a property for obtaining the raw details (that only works if raw details were set on create, i.e. in deserialization situations), and have a method that lets you access a detail by index and type hint.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ApplicationError implementation and trace its deserialization path. Work out how lazy details, raw details when available, and indexed access with a type hint should coexist. Done means deserialized errors expose the requested access patterns without losing the existing raw Python details behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100