Skip to content

Refactor autoschedule functionality #2868

Description

@andchiind

Describe the improvement you would like to see
Currently the database models and the way they are fetched in the hosted service is rather confusing. The Time and Day model for instance does not need to be its own table. Potentially we could just have a single table which stores a list of times as a single database value (not its own table), and a missiondefinition ID. Alternatively each mission definition could just store the list of

How will this change existing functionality?
It will make the code easier to maintain, and will simplify the database model.

How will this improvement affect the current Threat Model?
N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    improvementImprovement to existing functionality

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions