Entity UIs: delete obsolete filing header properties
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
The Filings UI was recently refactored / cleaned up (re: updated ledger). It was found that some header properties (in the `tasks` response - task and todo items) may be obsolete. If so then they can be deleted to clean up the code.
For example:
- certifiedBy
- effectiveDate
- email
- inColinOnly
- isFutureEffective
- submitter
To do:
- [ ] verify in all UIs whether the subject properties are indeed obsolete
- [ ] delete their usage in the UIs
- [ ] delete them from the API tasks response
(*) The single-filings call may also be returning these header properties.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Filings UI, the tasks response, and the single-filings call mentioned in the issue, checking each UI for use of the listed header properties. Done means obsolete properties are removed from all UIs and from the API response, with no remaining usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, python
- Domain
- api, backend, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100