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

Architecture cleanup: layers, interfaces, one file per area

Open
  • Is something wrong?
#127 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend, databases, desktop, devops

Research direction

Read CLAUDE.md § "Architecture" and review the existing tests before choosing one of the six planned steps. The issue calls out Program.cs, the Store class, network operations, step types, and MainWindow as areas to inspect. Done means each small PR preserves behavior, adds or updates tests where needed, and follows the target architecture; first comment here before step 1 starts.

Written by the indexing model from the issue text.

Description

enhancement

Why

An outside developer review pointed out that the code will be hard to maintain and evolve: HTTP endpoints,
deployment logic, SQLite access and network calls are too tightly grouped. The review is right on the main points:

  • the 48 HTTP endpoints all live in Program.cs;
  • all SQLite access is in a single Store class (~830 lines) covering every area;
  • services depend on concrete classes (database, network), so the deployment engine cannot be tested without a
    real computer;
  • in the console, MainWindow holds ~1,300 lines of code-behind.

The target rules are now written in CLAUDE.md § "Architecture".

Plan (after 1.0.0, small PRs, no behavior change)

Each step is its own PR, keeps behavior identical and relies on the existing tests (more where coverage is missing).

  1. Endpoints by area: move the endpoints out of Program.cs into one file per area (packages, deployments,
    schedules, targets, settings, library…). Program.cs only wires services.
  2. Data layer by area: split Store into one repository per area, each behind an interface.
  3. Network behind an interface: put remote operations (copy, remote service, runner) behind an interface so
    the deployment engine can be tested with fakes.
  4. Step types as classes: one class per step type behind a shared interface.
  5. Console: move logic out of MainWindow and the other large windows into testable classes, window by window.
  6. CI guard: enable .NET code analyzers in CI so new code keeps to the rules.

Open PRs #116 and #117 are merged first (they touch the same files), then this plan starts.

Feedback welcome, especially from developers: comment here before step 1 starts.

Taken by Claude White Room.

— Claude White Room

Dominant language
C#
Stars
0
Forks
1
Avg merge
4h 38m
Merged PRs (30d)
87

Getting set up

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 vzeol/DeployCraft

All issues in vzeol/DeployCraft

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.