Stateful

A state machine gem with built in categorization and workflow events. Works with plain ruby objects and Mongoid. It supports the following:

• Supports virtual/grouped states that can be used to break down top level states into more granular sub-states.
• Utilizes ActiveSupport::Callbacks
• Simple hash structure for defining states and their possible transitions. No complicated DSL to learn.
• ActiveSupport is the only dependency.
• Very small code footprint.
• Mongoid support, automatically creates field, validations and scopes for you.
• Supports multiple state fields on the same object
• Flexible design support both an "event driven" style of state changes where specific methods are called as well as an implicit style where you set the state field directly and configure callbacks to handle specific transitions.

Installation

Add this line to your application's Gemfile:

gem 'stateful'

And then execute:

$ bundle

Or install it yourself as:

$ gem install stateful

Usage

class Project
    include Stateful

    attr_reader :published_at

    stateful default: :draft,
             events: [:publish, :unpublish, :approve, :complete, :mark_as_duplicate],
             states: {
                active: {
                    draft: :published,
                    published: {
                        needs_approval: [:approved, :duplicate, :draft],
                        approved: :closed
                    }
                },
                inactive: {
                    completed: nil,
                    duplicate: nil
                }
             }

    def publish
        # change the state to needs_approval and fire publish events. The block will only be
        # called if the state can successfully be changed.
        change_state(:needs_approval, :publish) do
            @published_at = Time.now
        end
    end

    # use callbacks if you want
    after_publish do |project|
        NotificationService.notify_project_published(project)
    end

    # define other event methods ...
end

project = Project.new
project.active? # => true
project.draft? # => true
project.published? # => false

If you are using with Mongoid a field called state will automatically be created for you.

class Project
    include Mongoid::Document # must be included first
    include Stateful

    field :published_at, type: Time

    stateful default: :draft,
             events: [:publish, :unpublish, :approve, :complete, :mark_as_duplicate],
             states: {
                active: {
                    draft: :published,
                    published: {
                        needs_approval: [:approved, :duplicate],
                        approved: :closed
                    }
                },
                inactive: {
                    completed: nil,
                    duplicate: nil
                }
             }


    # ...
end

# you can allow states to transition to any other state using :*
class Project
    include Mongoid::Document
    include Stateful
    stateful default: :draft, states: {
         :draft => :*,
         :published => :*, 
         :archived => :draft # can only change to draft
       } 
                    
end

# scopes are automatically created for you
Project.active.count
Project.published.count

State Event Helpers

Two forms of change state methods are provided. There is the change_state method that was demonstrated above and then there is the change_state! version, which will raise an error instead of returning false if the state cannot be changed.

change_state and change_state! are great low level utilities for changing the state of the object. However one issue is that sometimes you wish to provide both a bang and non-bang version of an event method. For example:

def publish
  change_state(:needs_approval, :publish) do
    @published_at = Time.now
  end
end

def publish!
  change_state!(:needs_approval, :publish) do
    @published_at = Time.now
  end
end

Clearly this is not very dry. You could dry it up some more by using a callback, such as like this:

def publish
  change_state(:needs_approval, :publish)
end

def publish!
  change_state!(:needs_approval, :publish)
end

before_publish do
  @published_at = Time.now
end

However this is not much better. Especially if there is additional logic contained within the publish methods. Because of this there is an additional class helper called state_event that you can use to define both publish and publish! while only having to declare the logic once.

state_event :publish do
  transition_to_state(:published) do
    @published_at = Time.now
  end
end

So what is going on here? The state_event method is being passed the event name, which causes both the publish and publish! methods to be created. Additionally there is a new instance method available that is called transition_to_state(new_state). When this method is invoked it will in turn call either change_state(new_state, :publish) or change_state!(new_state, :published)

Note that transition_to_state is only meant to be called while one of the the event methods (in this example either publish or publish!) are being invoked. Calling this method any other time will raise an error.

Also note that currently state_event does not support handling method arguments. This is a planned feature but for now, if you need to support both bang and non-bang versions than you will need to use the lower level change_state method.

Validations

By default the only validations that take place is that Stateful checks that a defined state value has been set. A validation error will be added if an undefined or "group" state is set as the value.

Transition Validations

You can also enable validations that check that a state has been changed to a valid transition. If you are only setting the state value through explicit state events then you shouldn't need to worry about this, however if you intend on changing states by setting the state value directly, then you will likely want to use this setting.

Note: Validations are only tested with Mongoid but they should work for any ActiveRecord compatible interface.

class Project
    include Mongoid::Document 
    include Stateful
    stateful default: :draft, validate: true, states: {
         :draft => :*,
         :published => :*, 
         :archived => :draft
       } 
                    
end

project.state = :archived
project.save!

project.state = :published
project.save! # raises error

before_save/after_save/before_valadation/after_validation/validate callbacks

You can specify callbacks to fire when states are transitioned from one state to another. This is particulary useful when you are not using explicit event style methods for changing state but instead using validate: true and setting the state field directly.

class Project
  include Mongoid::Document
  include Stateful

  stateful default: :draft, validate: true, states: {
    :draft => :*,
    :published => :*,
    :archived => :draft
  }

  field :published_at, type: Time
  field :prevent_unarchive, type: Boolean

  # called before save
  before_transition_from(:draft).to(:published) do
    self.published_at = Time.now
  end

  # called before save
  before_transition_from(:published).to(:draft) do
    self.published_at = nil
  end
  
  # called after save
  after_transition_from(:published).to(:archived) do
    # some sort of follow up code like sending a notification
  end

  # you can use :* to specify any "from" or "to" state.
  validate_transition_from(:archived).to(:*) do
    if prevent_unarchive
      errors[:state] << "unarchiving has been disabled"
    end
  end
end

There is also a "when" DSL which allows you to only specify the from/to conditions once for multiple callbacks.

when_transition.from(:*).to(:published)
    .before_save do
        # before save
    end
    .after_save do
        # after save
    end
    .validate do
        #validation code
    end

TODO

• While the codebase is considered stable and tested, it is in a huge need of refactoring as its design has evolved significatly beyond its original scope.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request