Join: travel through nested contexts recursively
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 990
- Forks
- 45
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
The recursive helper should travel recursively through nested errors when built with oops.Join(err1, err2, err3).
On collision of error attribute, we have priority rules. We use the deepest code, time, duration, domain...
When OopsError wraps multiple errors, how to change this rule?
Contributor guide
No contributing guide indexed for this repository
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 in error.go at the recursive helper around line 666 and trace how oops.Join(err1, err2, err3) handles nested errors and colliding attributes. Determine and document the intended priority rule for multiple wrapped errors, then add coverage showing recursive traversal and the resulting attribute values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100