A tool for modeling events that happen in your application.

TODO: More on interactor concept

Interactor provided a behaviour and functions to execute the behaviours.

To use simply use Interactor in a module and implement the handle_call/1 callback. When use-ing you can optionaly include a Repo option which will be used to execute any Ecto.Changesets or Ecto.Multi structs you return.

Interactors supports three callbacks:

• before_call/1 - Useful for manipulating input etc.
• handle_call/1 - The meat, usually returns an Ecto.Changeset or Ecto.Multi.
• after_call/1 - Useful for metrics, publishing events, etc

Interactors can be called in three ways:

• Interactor.call/2 - Executes callbacks, optionaly insert, and return results.
• Interactor.call_task/2 - Same as call, but returns a Task that can be awated on.
• Interactor.call_aysnc/2 - Same as call, but does not return results.

Example:

defmodule CreateArticle do
  use Interactor, repo: Repo

  def handle_call(%{attributes: attrs, author: author}) do
    cast(%Article{}, attrs, [:title, :body])
    |> put_change(:author_id, author.id)
  end
end

Interactor.call(CreateArticle, %{attributes: params, author: current_user})