Helper functions to get available states by "categories" about oban HOT 3 CLOSED

Thanks for explaining your use case. I've thought about this a bit, and I'm not convinced it's valuable to break 7 states into 4 groups with fuzzy names and ambiguous definitions. For example, retryable is a "failure" state, and cancelled doesn't necessarily mean there was a failure.

I'm in favor of enhancing state definitions, but these helpers are something you'll have to add to your application.

from oban.

Thanks for the suggestion (and the PR). Can you provide a concrete use case for categories of job states?

from oban.

Sure, I can, the following example is a piece of code that I'm using to list the reports requests that can fail for a bunch of reasons and I need show if the report(represented by a Oban.Job) is running, crashes or if it running/waiting, so I query the jobs and show then in a phoenix template that has this function:

  def status(status) do
    cond do
      status in ~w(available retryable scheduled) -> "Waiting"
      status == "completed" -> "Finished"
      status == "executing" -> "Running"
      true -> "Failed"
    end
  end

But is weird my interface layer knows by hard code the states of Oban, so this can turn into:

def status(status) do
  case status do
    status when status in Oban.Job.states(:waiting) -> "Waiting"
    status when status in Oban.Job.states(:up) -> "Running"
    :completed -> "Finished"
    _ -> "Failed"
  end
end

from oban.