Persistence abstraction

[connors511]

Would you be open to the introduction of a repository to make the persistence of models abstract?

I'm not thinking any massively crazy refactor, but basically just a repository that persists (and fetches) the eloquent models, instead of calling save() directly on the model like here

My motivation for this is

1. Be able to use an in memory repository in my current project during tests
2. Have an easy way to hook into loading/saving the models for extra metadata

[ksassnowski]

This is something that I considered and eventually decided against when I first created the package. I'm not opposed to the idea in general, but I think it would require quite a few changes. If the Workflow no longer saves itself, it means that the entire control flow needs to change since something outside the workflow needs to pass it to the repository.

The easiest way to do this might be to have the onJobFinished and onJobFailed methods accept a repository as a parameter and then use that instead of $this->save(). This seems like a rather half-hearted implementation, however.

What are your thoughts/plans?

[connors511]

I didn't have any concrete plans, but the first (naive) idea that sprung to mind was just pulling it from the container like AbstractWorkflow does, but that's pretty nasty too.

I can dig around some more and try some stuff out.