Address Coexistence of Legacy and New Project Models #1337

New issue

Open

opened 2026-04-02 16:53:56 +00:00 by freemo · 0 comments

freemo commented

2026-04-02 16:53:56 +00:00

Owner

The coexistence of the legacy Project model (src/cleveragents/domain/models/core/project_legacy.py) and the new NamespacedProject model (src/cleveragents/domain/models/core/project.py) is a major architectural concern.

Key Issues:

Confusion and Inconsistency: The two models have different identifiers (integer ID vs. namespaced name), different attributes, and different semantics. This is a source of confusion and will lead to inconsistent usage.
No Clear Migration Path: There is no clear plan for migrating from the legacy model to the new one. This will make it difficult to deprecate and remove the legacy model.
Potential for Data Loss: The migration from the legacy model to the new one could result in data loss if not handled carefully.

Recommendation:

Establish a clear plan for migrating from the legacy Project model to the new NamespacedProject model. This plan should include:

A timeline for deprecating and removing the legacy model.
A clear mapping between the fields in the legacy model and the new model.
A strategy for migrating existing data.
A set of integration tests to ensure the migration is working correctly.

The coexistence of the legacy `Project` model (`src/cleveragents/domain/models/core/project_legacy.py`) and the new `NamespacedProject` model (`src/cleveragents/domain/models/core/project.py`) is a major architectural concern. **Key Issues:** * **Confusion and Inconsistency:** The two models have different identifiers (integer ID vs. namespaced name), different attributes, and different semantics. This is a source of confusion and will lead to inconsistent usage. * **No Clear Migration Path:** There is no clear plan for migrating from the legacy model to the new one. This will make it difficult to deprecate and remove the legacy model. * **Potential for Data Loss:** The migration from the legacy model to the new one could result in data loss if not handled carefully. **Recommendation:** Establish a clear plan for migrating from the legacy `Project` model to the new `NamespacedProject` model. This plan should include: * A timeline for deprecating and removing the legacy model. * A clear mapping between the fields in the legacy model and the new model. * A strategy for migrating existing data. * A set of integration tests to ensure the migration is working correctly.

Rows
Columns