check-architecture

Architecture Check

Verify the project follows its architectural rules. Run automated arch tests first, then supplement with manual checks.

Configuration

Read cloudstack.json from the project root at the start of execution. Extract:

• NAMESPACE = project.namespace (default: detect from *.sln name or first *.csproj root namespace)
• SERVICES = backend.services[] (default: discover from src/*/ directories containing .Application/ subfolders)
• SOLUTION = backend.solutionPath (default: find *.sln in src/)

If cloudstack.json does not exist, auto-detect by scanning the project structure.

1. Run NetArchTest.Rules Tests

First, run any architecture tests in the test suite:

dotnet test {SOLUTION} --filter "FullyQualifiedName~Arch" --no-restore

If no arch tests exist, proceed with manual checks below.

2. Layer Dependency Violations

For each service in {SERVICES}, check that the Domain layer does not reference Infrastructure or Host:

# Domain must not reference Infrastructure or Host
grep -rn "using.*Infrastructure\|using.*Host" src/{Service}/**/Domain/ --include="*.cs"

# Application must not reference Host
grep -rn "using.*Host" src/{Service}/**/Application/ --include="*.cs"

Report each violation with the file path and offending using statement.

3. Result Pattern Compliance

For each handler file in src/**/Application/**/*Handler.cs, check for thrown business exceptions:

# Handlers should return Result<T>, not throw exceptions
grep -rn "throw new.*Exception" src/**/Application/ --include="*Handler.cs"

Acceptable throws (exclude these from violations): ArgumentException in value object constructors, InvalidOperationException for programmer errors, NotImplementedException for placeholder code.

If no handler files changed, skip this check.

4. CQRS Conventions

Verify:

• Command records are in Application/Commands/ folders
• Query records are in Application/Queries/ folders
• Command handlers don't use query-only repositories for writes
• Query handlers don't call write repositories