deptrac-fixer

Deptrac architectural violations are fixed by refactoring code to respect hexagonal boundaries. This involves applying documented patterns like Command Bus and factories to correct cross-layer dependencies, such as domain importing frameworks or infrastructure calling application handlers.

Domain layer Deptrac violations occur when domain code imports external frameworks. These forbidden dependencies are resolved by applying pragmatic refactoring patterns that align code with domain boundaries without modifying the deptrac.yaml configuration file.

Yes, forbidden dependencies can be resolved without editing deptrac.yaml. The code is automatically refactored to satisfy Deptrac rules by applying structural patterns that respect hexagonal architecture boundaries between domain, application, and infrastructure layers.

Aligning a codebase with hexagonal architecture involves applying specific fix patterns to the violations reported by Deptrac. The automated correction process maps dependencies correctly, ensuring infrastructure does not directly call application handlers and domain remains isolated.

Start by running make deptrac to detect architectural violations. Once cross-layer dependency violations are reported, apply automated corrections that refactor the codebase to align with documented hexagonal architecture fix patterns.

Fixing cross-layer dependency violations applies patterns like Command Bus and factories. These pragmatic refactoring approaches align code with domain boundaries for issues such as Domain to Doctrine mapping or Infrastructure to Handler dependencies.