Expand description
Fix engine core types.
Defines the data model for planned fixes: text edits grouped by file, with support for pattern-based (deterministic) and LLM-assisted fixes.
Modules§
- incident
- Incident types representing matched violations in source code.
- report
- Konveyor output format types.
- rule
- Konveyor rule definition types.
Structs§
- FixPlan
- A fix plan: all planned fixes grouped by file.
- FixResult
- Result of applying a fix plan.
- FixStrategy
Entry - A machine-readable fix strategy entry.
- LlmFix
Request - A request to send to the LLM for fix generation.
- Manual
FixItem - An incident that requires manual fixing.
- Member
Mapping Entry - A member-level mapping entry for structural migration strategies.
- Planned
Fix - A planned fix for a single incident.
- Rename
Mapping - A rename mapping: old name -> new name. Used for prop renames, component renames, import renames, etc.
- Strategy
Mapping Entry - A single from/to mapping within a consolidated fix strategy.
- Text
Edit - A single text replacement within a file.
Enums§
- FixConfidence
- How confident the fix guidance is.
- FixSource
- Where the fix guidance originates.
- FixStrategy
- Known fix strategies keyed by rule ID. Each entry defines how to transform incidents from that rule into text edits.
Functions§
- load_
strategies_ and_ families - Load fix strategies from a JSON file and also extract raw family-level
FixStrategyEntryentries (keyedfamily:*) for use in family consolidation. - load_
strategies_ from_ json - Load fix strategies from a JSON file.
- strategy_
entry_ to_ fix_ strategy - Convert a
FixStrategyEntry(from the sharedkonveyor-corecrate) to a runtimeFixStrategy.
Type Aliases§
- Strategies
AndFamilies - Return type for
load_strategies_and_families:(strategies, family_entries).