component-common-domain-detection

Consolidate duplicate domain components by scanning namespaces and imports to group identical leaf-node logic, then comparing functionality to recommend a shared service, shared library, or merge approach. This identifies overlapping notification, audit, or validation logic for safe refactoring.

Afferent coupling analysis measures how many other components depend on a specific module before and after consolidation. You need it during refactoring to verify that merging duplicate domain logic does not accidentally introduce hidden coupling regressions or architectural bottlenecks.

Detect shared classes by scanning import statements across the codebase and classifying usage as either domain or infrastructure. This identifies modules reused in multiple components, enabling accurate functionality comparison and safe consolidation planning for domain-specific logic.

Yes, namespace pattern detection scans for identical leaf-node names like notification, validation, formatting, and audit across components. It groups these matching namespaces to evaluate implementation similarity and determine if a shared library or service consolidation is feasible.

Refactor shared services by classifying detected imports as domain versus infrastructure before consolidation. This distinction ensures that only reusable business logic is centralized into a shared service or library, preventing accidental coupling with unrelated infrastructure code.

Avoid a component merge when afferent coupling analysis reveals that combining duplicate domain logic would create a dependency bottleneck. If post-consolidation coupling is too high, a shared library or shared service approach is recommended instead of a full component merge.