component-flattening-analysis

To find orphaned classes in root namespaces, you map the component namespace structure to detect root namespaces and identify files lacking proper hierarchy. The analysis classifies these orphaned files as shared, domain, or mixed to guide safe refactoring.

Component flattening is the process of removing component nesting by ensuring components exist only as leaf nodes. You need to flatten component hierarchies when orphaned classes appear in root namespaces, violating the structural architecture of your codebase.

To create a refactoring plan, you assess orphaned files and analyze flattening strategies like Consolidate Down, Split Up, or Move Shared Code. This produces a structured flattening plan with prioritized steps to guide safe component hierarchy refactoring.

Yes, you can analyze component structure to map namespace structures and detect hierarchy violations without moving files. The analysis generates hierarchy reports and proposes flattening strategies before any actual file movement or import updates occur.

Component flattening analysis limitations include the requirement to move files and update imports to execute the proposed plan. While it maps namespaces and detects violations, applying the actionable refactoring plan requires safe execution steps to avoid breaking dependencies.