[FEAT-API]: Damage Functions Backend
Open
Nobody has claimed this yet.
3SP
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- get the user inputs from https://github.com/USACE/go-consequences/blob/main/structures/occtypes.json
- build out a table for damage function
- confirm inputs with @trietmnj
- include error handling to ensure the header columns and data is in the correct format
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
Start by reading structures/occtypes.json in the linked go-consequences repository to identify the user inputs and expected fields. Confirm the inputs with @trietmnj before locating the chart-docs backend entry point for the damage-function table. Done means the table is built and header and data formats have error handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100