18 static dimensions cover complete Odoo code diff, plus git history change trajectory as 19th dimension.

No modules need to be installed on source/target systems - just source code paths for complete diff analysis.

1)    Module dimension: compare module lists between versions, identifying added, removed, changed modules.

2)    Object dimension: compare model definitions, identifying added, removed, changed fields and methods.

3)    Field dimension: compare field attributes, identifying changes in type, length, default values.

4)    View dimension: compare view definitions, identifying structural and attribute changes.

5)    Method dimension: compare method definitions, identifying signature and implementation changes.

6)    Git history dimension: analyze git commit history, capturing complete change trajectories including renames and refactors.

Auto-derive third-party module upgrade mapping from diff data without manual rule writing.

module.upgrade.rule derives mapping from diff, with git history rename detection for complex scenarios.

1)    Field mapping: auto-derive old-to-new field mappings including renames and type conversions.

2)    Method mapping: auto-derive old-to-new method mappings handling renames and signature changes.

3)    View adaptation: auto-adjust view definitions for new version view conventions.

4)    Data migration: auto-generate data migration scripts for field value conversions and format changes.

5)    Git history rename detection: analyze git history for code renames, ensuring accurate upgrade mapping.

Transform diff data into third-party module upgrade code, reusing rendering pipeline.

Generated code includes Python code, data files, view files, covering complete upgrade needs.

1)    Python code: generate model inheritance, field redefinition, method override code.

2)    Data files: generate data migration scripts for field value conversions and format changes.

3)    View files: generate view inheritance and adjustment code for new version conventions.

4)    Rendering pipeline reuse: reuse code generation engine's rendering pipeline for quality.

Detect potential bugs in third-party modules during upgrade, with bug truth library for precise detection.

third.party.bug.checker detects potential bugs based on diff data and bug truth library.

1)    Field reference check: detect if fields referenced by third-party modules still exist in new version.

2)    Method reference check: detect if methods called by third-party modules have compatible signatures.

3)    View compatibility check: detect if third-party view definitions are compatible with new version engine.

4)    Bug truth library: accumulates known bug patterns for precise matching.

5)    Validation reports: auto-generate validation reports after migration, with configurable rules.