Skip to content

General "Job" Base Class #36

Description

@Poofjunior

The current job has a wash_step field, which is a list of wash steps. Not all machines will necessarily run this function, so we should make this list of steps more generic and support subclassing so that specific machine jobs can run a specific list of steps with specific parameters and get validation for those specific types of steps.

One way do that, would need:

  • a job base class
  • a brainwasher derived class which is equivalent to the current Job class
  • a brainslosher derived class with a distinct step to execute

Another way might be:

  • a generic job base class
    • a function or method name that is the name of the function to execute in a list of steps
  • the brainwasher specifies the run_wash_step function
  • the brainslosher specifies a run_cycle function (or similar)

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions