Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEAT-Infra]: Research how to properly handle converting to single API

Open
  • Is something wrong?
#758 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
backend-api-design

Research direction

Start by mapping the current file structure and the concurrent file additions, updates, and deletions described in the issue. Document the high-level impact of converting to a single API, how to avoid large merge conflicts while work continues, and the ordered steps for beginning the process.

Written by the indexing model from the issue text.

Description

  • how to do this while working in the backgorund to not cause giant merge conflicts. Entire file sctructures will be altered, while at the same time progress is being made on other fronts (files updates, files added & delete etc.)
  • basic high level on what this will impact
    -basic steps that should be taken in order to start the process
Dominant language
No language data
Stars
2
Forks
0
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

  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.