Recipients handling for OutboxService
Open
Nobody has claimed this yet.
1. to develop
enhancement
skill:backend
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
We have the Recipient object but pass around plain arrays most of the time.
Describe the solution you'd like
Use Recipient object
Describe alternatives you've considered
No response
Additional context
No response
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
Locate OutboxService and the Recipient object, then inspect where recipient arrays are currently passed around. The change is complete when OutboxService uses Recipient objects consistently and the existing recipient-handling behavior remains covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100