Filer - investigate what needs to be done with COOP specific logic in IA processor
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
There is COOP specific logic that has been commented out in the IA filing processor along with a note that it should be removed. Some investigation needs to happen to determine what removing this actually means and if there is any downstream work required.
**NOTE:**
* might need to consult Relationships team.
* If there is work to be done here and it fits within the scope of this estimate, then complete the work. If it doesn't fit, in estimate, that's okay this was estimated high for unknown and needing input from outside of our core team
**TODOs**
- [ ] Review[ commented out code ](https://github.com/bcgov/lear/blob/99718698dc22610c847cceef5cc19b3a3cfc4c26/queue_services/entity-filer/src/entity_filer/filing_processors/incorporation_filing.py#L77-L109)in IA filing processor
- [ ] Determine what downstream affects this has
- [ ] Determine if any new tickets need to be created based upon results of investigation
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the commented-out COOP-specific code in queue_services/entity-filer/src/entity_filer/filing_processors/incorporation_filing.py at lines 77-109. Consult the Relationships team as needed and trace any downstream effects. Done means documenting whether removal requires changes and creating follow-up tickets when appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100