[FEAT-API]: Damage Functions Backend

Open
#650 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go
Domain
api, backend

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.

Description

3SP
Dominant language
No language data
Stars
2
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from USACE/chart-docs

All issues in USACE/chart-docs

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.