[FEAT-API/Infra]: Phase 1 of merging SCT and FEAT API's
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- api, infrastructure
Research direction
Start by reading the linked issue, https://github.com/USACE/chart-docs/issues/758, for the scope of Phase 1. This issue does not name files, tests, or completion criteria, so those need to be established from the linked issue before work can begin.
Written by the indexing model from the issue text.
Description
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from USACE/chart-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
USACE/chart-docs#756 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
USACE/chart-docs#750 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
USACE/chart-docs#761 ·
-
[FEAT-API/UI]: Add ability to download hydrograph input / outputPossibly taken @noarevalo-bah claimed this 4 days ago. Open
USACE/chart-docs#759 · 1 assignee ·
-
[FEAT-Infra]: Research how to properly handle converting to single APIPossibly taken @martyheynbah claimed this 5 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
USACE/chart-docs#758 · 7 comments · 1 assignee ·
All issues in USACE/chart-docs
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
backend dev experience good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cuttle-cards/cuttle#1401 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
btclib-org/btclib-wallet#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/langmem#194 ·