Angular Modernizer
    Preparing search index...

    Interface PlanMigrationResult

    Plan migration tool result.

    interface PlanMigrationResult {
        alternativeStrategies: MigrationStrategy[];
        notes?: string[];
        planSource: "scan" | "template";
        reasoning: {
            constraintImpact: string[];
            primaryFactors: string[];
            riskAssessment: string;
        };
        recommendedStrategy: MigrationStrategy;
        roadmap: {
            milestones: string[];
            phases: {
                deliverables: string[];
                duration: string;
                name: string;
                steps: MigrationStep[];
            }[];
            totalDuration: string;
        };
        scanPlan?: ScanPlanOutput;
        stepsWithStyleAnalysis?: {
            alignsWithStyle: boolean;
            step: MigrationStep;
            styleAlignmentScore: number;
            styleWarnings: string[];
        }[];
        styleAlignmentScore?: number;
        styleAwareRiskAssessment?: StyleAwareRiskAssessment;
        styleConflictingSteps?: {
            conflictReason: string;
            stepName: string;
            styleRecommendation: string;
        }[];
        styleRecommendations?: {
            affectedSteps: string[];
            category: "architecture"
            | "rxjs"
            | "di"
            | "state-management"
            | "naming";
            currentStyle: string;
            reasoning: string;
            recommendation: string;
        }[];
        successMetrics: string[];
        summary: string;
        warnings?: string[];
    }
    Index

    Properties

    alternativeStrategies notes? planSource reasoning recommendedStrategy roadmap scanPlan? stepsWithStyleAnalysis? styleAlignmentScore? styleAwareRiskAssessment? styleConflictingSteps? styleRecommendations? successMetrics summary warnings?

    Properties

    alternativeStrategies: MigrationStrategy[]

    Alternative strategies.

    notes?: string[]

    Why the scan-based plan was not built although violations had files.

    planSource: "scan" | "template"

    scan when the roadmap was built from file-level violations, template when it comes from the strategy templates.

    reasoning: {
        constraintImpact: string[];
        primaryFactors: string[];
        riskAssessment: string;
    }

    Strategy selection reasoning.

    Type Declaration

    • constraintImpact: string[]

      How the constraints influenced the choice.

    • primaryFactors: string[]

      Main factors behind the choice.

    • riskAssessment: string

      Risk assessment of the choice.

    recommendedStrategy: MigrationStrategy

    Recommended migration strategy.

    roadmap: {
        milestones: string[];
        phases: {
            deliverables: string[];
            duration: string;
            name: string;
            steps: MigrationStep[];
        }[];
        totalDuration: string;
    }

    Implementation roadmap.

    Type Declaration

    • milestones: string[]

      Milestones of the roadmap.

    • phases: {
          deliverables: string[];
          duration: string;
          name: string;
          steps: MigrationStep[];
      }[]

      Roadmap stages in execution order.

    • totalDuration: string

      Estimated total duration as text.

    scanPlan?: ScanPlanOutput

    File-level plan (scan-based planning only).

    stepsWithStyleAnalysis?: {
        alignsWithStyle: boolean;
        step: MigrationStep;
        styleAlignmentScore: number;
        styleWarnings: string[];
    }[]

    Migration steps with style alignment scores.

    Type Declaration

    • alignsWithStyle: boolean

      true when the score reaches styleAlignmentThreshold.

    • step: MigrationStep

      The analyzed step.

    • styleAlignmentScore: number

      Style alignment score of the step.

    • styleWarnings: string[]

      Style problems of the step.

    styleAlignmentScore?: number

    Overall style alignment score (0-100).

    styleAwareRiskAssessment?: StyleAwareRiskAssessment

    Style-aware risk assessment (when styleProfile is provided).

    styleConflictingSteps?: {
        conflictReason: string;
        stepName: string;
        styleRecommendation: string;
    }[]

    Steps that conflict with codebase style conventions.

    Type Declaration

    • conflictReason: string

      Why the step conflicts with the codebase style.

    • stepName: string

      Name of the conflicting step.

    • styleRecommendation: string

      How to keep the style.

    styleRecommendations?: {
        affectedSteps: string[];
        category: "architecture" | "rxjs" | "di" | "state-management" | "naming";
        currentStyle: string;
        reasoning: string;
        recommendation: string;
    }[]

    Style preservation recommendations.

    Type Declaration

    • affectedSteps: string[]

      Names of the affected steps.

    • category: "architecture" | "rxjs" | "di" | "state-management" | "naming"

      Style area.

    • currentStyle: string

      Current style of the codebase.

    • reasoning: string

      Why the recommendation applies.

    • recommendation: string

      Recommendation.

    successMetrics: string[]

    Success metrics.

    summary: string

    Human-readable summary for LLM consumption.

    warnings?: string[]

    Conditions that can make the scan-based plan incomplete (unresolved library imports).

    Settings

    Member Visibility

    On This Page

    Properties