[SCT-Workflow][Bug]: Make Evac Rate a Required Field in COA Details Page
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
Per Triet's previous comment:
A condition where the aggregation wouldn't work is when the evac_rate is empty in the COA edit page. Maybe we should make the evac_rate field required.
Make the Evac Rate field in the Scope COA Edit Page a required field.
Steps to Reproduce
Go to Scope COA tab, click the document icon in the left nav bar, then click on 'Add Scope COA' or an existing COA.
Expected Behavior
Evac_Rate field should be a required field for saving.
Device / System
laptop
Screenshots
No response
Additional Details
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the Scope COA tab, use the document icon, and inspect the Add Scope COA and existing COA edit flows described in the issue. Trace how Evac_Rate is validated during save; done means an empty Evac_Rate cannot be saved in either flow and a populated value still saves successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100