feat: scaffold .NET backend solution with Clean Architecture #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/backend-scaffold"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Scaffolds the initial .NET backend solution with Clean Architecture / Ports & Adapters structure.
What's included
Solution structure
Dependency direction (enforced via project references)
Key details
dotnet tool restore)/healthendpoint and OpenAPIVerification
dotnet build→ ✅ 0 errors, 0 warningsdotnet test→ ✅ 4/4 tests passdotnet ef --version→ ✅ EF Core 10.0.9Related ADRs
🤖 Hermes automated review: minor comments
I reviewed the PR diff for the initial backend scaffold. This is a conversation-level review comment; the current Forgejo MCP integration does not support true inline review comments or formal approval/request-changes states.
Minor findings
backend/src/DoujinManager.Server/Program.cs:1and related server files — CRLF line endings makegit diff --checkfailgit diff --check fd6353c...ce996a1reports trailing whitespace on every line of several newly-added server files because they are committed with CRLF endings while the rest of the scaffold is LF. Affected files includebackend/src/DoujinManager.Server/DoujinManager.Server.csproj,Program.cs,Properties/launchSettings.json,appsettings.Development.json, andappsettings.json..gitattributespolicy if CRLF is intentional.Checks
dotnet build --no-restore backend/DoujinManager.slnxcould not run because NuGet assets were not present (project.assets.jsonmissing); no restore/install was performed in this cron job.Automated daily review. I never merge PRs.