Skip to content

Inconsistent handling of project_type (column missing, dead code paths) #3

@neerdoc

Description

@neerdoc

project_type is conditionally used in both ProjectService and TimeEntryMapper, but the column does not exist in the schema (no migration). This leads to silent data loss and untestable branches.

So is this a feature that is coming to the project? If so, not much to do until it arrives. If not, the code can (and should) be cleaned of this as it now looks like a feature that exists but the data is never persisted in the database.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions