Emailer - update special resolution processor to work with alternate name changes
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Update email processor(s) such that we are able to work with alternate_name entries where required. With the new data model, SPs will need to use alternate_name similar to the way we use a legal_entity record.
**TODOs**
Do following for email processor(s) relevant to this ticket:
- [ ] Do work in legal name branch
- [ ] Update to work with alternate names and legal entities
- [ ] Update versioning logic where required. May be still using versioning approach used in old data model
- [ ] There may be some other misc updates required to get processor working. Update as appropriate.
- [ ] Update worker.py as required
- [ ] Update tests relevant to this email processor
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the relevant email processor(s), worker.py, and their existing tests; start by tracing how legal_entity entries and versioning are currently handled. Update the processor behavior for alternate_name entries and legal entities, adjust versioning as needed, and confirm the relevant tests cover the new data model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100