Create UI: add/update NR validation
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This may also apply to Edit UI. If those updates can't be done in this ticket then please create a new ticket.
A number of checks can be done to validate that a NR is acceptable for its current use (eg, full restoration). For example:
- its legal type (eg, ULC)
- its "request type code" (eg, ULCT)
- its "request action code" (eg, MVE)
- its state (eg, APPROVED)
- the applicant's email or phone (in fact, we should not allow fetching without those)
- the business ID (if the NR is for a particular restoration, etc)
These checks are not done in all cases (eg, new IA, restoration, limited resto conversion, change of name, etc). They should be added/updated accordingly.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the Create UI, the possible Edit UI, and any existing NR validation, then map the listed checks to each use case. Done means the appropriate validation is applied for every supported case, including required applicant contact details, with tests covering the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100