LVF: Corrections
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
- correct receiver filing
- correct liquidator filing
- correct TA filing
- correct dod?
- correct officers?
### Notes
- there is a singular correction filing type that covers all corrections for all filings
- currently there is a catch all correction page in the older UI where many edits are allowed on the current data of the business (whether the updates are relevant to the corrected filing or not is not validated)
- Backend
- Schema: relationships schema will need to be added into the correction schema
- API: lvf validation will need to be added into the corrections validation
- API: outputs logic will need to be verified (main concern will be business summary)
- Filer: processing for these will need to be added for the new corrected filing types
- Frontend
- correction page(s) (either catch all where you can change anything or per filing group)
- business dashboard - launch endpoint (will need to go to our new page(s) for LVFs) + enabling rules
-
Business and Validation Rules are captured in the Parent Ticket
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.